Docker Integration in Kubernetes: What Does the Removal of Dockershim Mean for You?

Introduction

The Kubernetes community is facing a significant change: the removal of the Dockershim component is imminent. This part of Kubernetes, which allows integrated use of the Docker Engine, will soon no longer be supported. But don’t worry, we’ll clarify what this means for you and your team!

What Specifically Changes for Developers/DevOps Teams?

The deprecation of Dockershim means that Kubernetes users who have been using Docker as their container runtime should switch to alternative runtimes. Kubernetes has already developed the Container Runtime Interface (CRI), which enables seamless integration with other container runtimes. Many developers and companies have already made this transition without encountering major issues. Nevertheless, Dockershim remains popular among many users, highlighting the need for careful planning and preparation.

The planned removal of Dockershim is scheduled for Kubernetes version 1.24, which is expected to be released in April next year. For those working with alpha and beta versions, Dockershim will be removed as early as December, at the start of the 1.24 development cycle.

Practical Examples or Use Cases

To facilitate the transition, there are already comprehensive migration guides for switching to other container runtimes. Users report positive experiences with runtimes like containerd or CRI-O, all of which run through the CRI interface.

An example: A team that previously used Docker was able to not only boost its performance but also reduce operational costs by migrating to containerd. This shows that the switch can be not only necessary but also beneficial.

The question remains: Are you ready for the removal of Dockershim? It is advisable to act now and initiate the necessary steps for migration.

At ayedo, we are happy to support you as a partner in implementing your Kubernetes project. Let’s ensure together that your team is optimally prepared for the changes!

Stay informed about developments and share your feedback with us! The community counts on your opinion!

Source: Kubernetes Blog