1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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
con risposta un anno fa
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 3 mesi fa
- AWS UFFICIALEAggiornata 2 anni fa
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 ?
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.