By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

How to handle docker deprecation after eks 1.24 upgrade?

0

As dockershim has been deprecated in eks 1.24 and containerd has become runtime, and I didn't completely understand the deprecation concept and upgraded my eks cluster (with managed nodegroups) from 1.23 to 1.24.

Since then, any new nodes joining the cluster are having docker daemon inactive, and all of my deployments are failing with an error: "Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?".

Now, what can be done exactly to fix this? Do I need to change all of my deployment related docker files or Can I configure something that the cluster still uses docker daemon?

Topics
ContainersDevOpsMicroservices
Tags
Amazon Elastic Kubernetes ServiceAmazon Elastic Container ServiceContainersDevOpsMicroservices
Language
English
repute
asked a year ago227 views
1 Answer
0

Hello There,

As a first step, you could look if you are affected by the removal of dockershim in this documentation.

Considering you are already affected by this post migration and based on your question you probably have some node startup scripts that use docker commands, you can now look at the guidance in this documentation to migrate away from using docker commands which won't work going forward.

There is also this very good blog post detailing all the necessary step to be containerd ready on amazon EKS.

Please let me know in case of any further queries.

Thanks, Manish

profile picture
Manish
answered 10 months ago
  • repute
    10 months ago

    But as the k8s documentation states, cri-dockerd can be used for docker engine dependency which I have, but eks doesn’t support configuring cri-dockerd on the cluster, how to overcome that ?

  • Manish
    10 months ago

    I would personally suggest, if possible you should look at removing the docker engine dependency as I can see a few issues listed here for installing cri-dockerd https://github.com/Mirantis/cri-dockerd/issues/204. Also I can see some issues raised here https://github.com/aws/containers-roadmap/issues/1514 where team suggested folks to rethink exposing docker sockets and running privileged containers which is an anti-pattern.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content