When working with Kubernetes for the first time, the concept of a pod feels strange because Docker has not prepared us for it ;-) But the idea of a pod can be useful when working with Docker. This post will demonstrate how to use a pod to deploy isolated environments for workshops.
In a workshop situation, attendees must be able to follow the material in a personal hands-on environment. Docker helps isolating such environments and prevents issues from using the attendees’ laptop. Let me show you how to provide dedicated environments using shellinabox.
I had the honour to contribute two workshops about Docker to an called Sommercampus held by the faculty of engineering of the university Freiburg:
The demos are part of the slides.
I am very happy to announce that I have been awarded Microsoft Most Valuable Professional (MVP) in Cloud and Datacenter Management again.
Thank you, Microsoft, for recognizing my contributions to the community.
This week, I attended a new kind of conferencecalled DevOps Essentials organized by dpunkt, heise Developer and iX. They decided to have most half-day workshops with only one keynote-like talk per day. I was able to contribute one of the half-day workshops for advanced users of Docker.
Products for continuous integration and continuous delivery have become a commodity. But among them is a growing number isolating build steps in containers. Instead of using a fully integrated product, I have created a tool called insulatr to execute builds in containers without the need for a server component or scheduler.
This week I had the opportunity to speak at the Azure and .NET Meetup Freiburg about developing PowerShell modules. Thanks for having me!
After one whole year, I was finally able to contribute another talk at DevMeetup Freiburg. It was about the security ups and downs of container management based on Docker.
ContainerConf marked a very special moment this year because I was able to contribute one workshop and two talks about Docker.
Publishing the Docker daemon usually involves creating the requires certificates, reconfiguring the Docker daemon and restarting it. But often, you do not have the necessary permissions to change the daemon configuration or restart it. I’ll demonstrate how to use a containerized reverse proxy to achieve the same.