Businesses are moving at different speeds on the road to containers. There’s a growing appreciation of the value of container technology (see my previous post The Irresistible Allure of Containers: 4 Big Benefits) and an ever-increasing number of implementations already in progress. Many organizations are now at the point where they’ve completed their initial proof of concept (PoC). But they’re wondering how to get from there to production, and how to sustain the momentum of their containerization effort as it runs into the complexities of operations.
Kubernetes and Docker Swarm are both popular and well-known container orchestration platforms. You don't need a container orchestrator to run a container, but they are important for keeping your containers healthy and add enough value to mean you need to know about them.
Today, I had the opportunity to speak at ContainerConf in Mannheim. I talked about the news in the Docker ecosystem with a special focus on the Moby project. This post not only publishes my slides but also the demos from this talk.
Going Production with Docker and Swarm Session Info Video of Session (forthcoming) Slides at SpeakerDeck Slide links: HPE and Docker White Paper on MySQL Performance Across VM's, Container's, and Bare Metal (I Co-Authored) GitHub Repo for the above white paper. Scripts and Dockerfiles for testing your VM and Bare Metal
Privileged containers have been the reason for many discussions. There are security minded people who would like to eliminate them as well as technical people who need the feature to drive containerization. I’d like to show you how to be a technical person running a privileged container but honour security considerations by dropping capabilities as soon as they are not required.
The article that follows is an extract from the last chapter of The DevOps 2.2 Toolkit: Self-Sufficient Docker Clusters book. It provides a good summary into the processes and tools we explored in the quest to build a self-sufficient cluster that can (mostly) operate without humans. We split the tasks that a self-sufficient system should…