Docker Captains speak bluntly: “Containerd is basically the real engine behind Docker”
Docker is revolutionizing IT — you’re probably hearing this phrase quite often. Still, these questions linger: If we were to look beyond the hype, what’s so disruptive about Docker technology? What are the differences between Docker and a virtual machine? What is hype and where does the real added value lie? We talked with Chanwit Kaewkasi about all this and more.
Docker manages to insert itself into all our conversations — why? Because it is extremely helpful and everyone loves it. There’s a lot going on in the Docker world (for example, the Docker platform and Moby Project are now integrating support for Kubernetes) but this is not why we’re doing this interview series with Docker Captains.
Don’t miss our Docker Captains interview series
We’d like to hear more about their love stories with Docker, their likes and dislikes, their battle scars and more. Without further ado, we’d like to introduce Chanwit Kaewkasi,Assistant Professor at Nakhon Ratchasima, Thailand.
JAXenter: Can you tell us a little bit about your first contact with Docker? Was it love at first sight?
Chanwit Kaewkasi: In our laboratory, we were searching for a virtualization layer to help manager our Big Data stack dated back to 2014. VM solutions were too heavy for us, and we were lucky enough to find Docker.
JAXenter: Docker is revolutionizing IT — that is what we read and hear very often. Do you think this is true? If we were to look beyond the hype, what’s so disruptive about Docker technology?
Chanwit Kaewkasi: It’s pretty true in my opinion. In the past, it was very hard to up and run a set of Web servers.
With Docker, we can just do it in a couple of minutes.
JAXenter: How is Docker different from a normal virtual machine?
Chanwit Kaewkasi: Docker is basically using the OS-level virtualization, Linux namespaces and control groups, for example. Its overhead is very thin compared to a virtualization technique, like Hypervisor used by virtual machines.
Containerd is basically the real engine behind Docker.
JAXenter: How do you use Docker in your daily work?
Chanwit Kaewkasi: I help companies in South-East Asia and Europe design and implement their application architectures using Docker, and deploy them on a Docker Swarm cluster.
JAXenter: What issues do you experience when working with Docker? What are the current challenges?
Chanwit Kaewkasi: Multi-cluster management is still not easy. I have to create my own tool to manage them.
It would be great if we can do this natively in Docker Swarm.
Multi-host networking is current good, but I still find some minor issues. However, it’s going to be better as many SDN vendors are implementing their own network stacks as Docker plugins. It’s a good news.
JAXenter: Talking about the evolution of the Docker ecosystem: How do you comment on Docker’s decision to donate containerd runtime to CNCF?
Chanwit Kaewkasi: It’s a great and cool move. Containerd is basically the real engine behind Docker. The standardized container runtime benefits everyone in the community.
Multi-cluster management is still not easy.
JAXenter: Is there a special feature you would like to see in one of the next Docker releases?
Chanwit Kaewkasi: Sure. I hope to see cluster namespacing and the network layer stabilization in the near coming releases.
JAXenter: Could you share one of your favorite tips when using Docker?
`docker system prune -f` always makes my day.