EKS has switched to containerd from docker, and dind mode configuration assumes dockerd

[alpozcan]

What would you like added?

My understanding is that we would have to deploy nerdctl or similar into our runner images if we want to do this seamlessly, but have to drop docker & docker-compose client tools in favour of this, at a minimum.

Are there any plans to support and/or document that setup? It could be just a matter of the two changes I mentioned above but not sure whether other assumptions are being made with regards to the use of Docker as the container runtime, so I'd like to see if anyone had success.

Why is this needed?

There is no more docker.sock on AWS EKS clusters, as they have been switched over to containerd. We now have/var/run/containerd/containerd.sock in its place, which is not the same thing interface-wise.

[github-actions]

Hello! Thank you for filing an issue.

The maintainers will triage your issue shortly.

In the meantime, please take a look at the troubleshooting guide for bug reports.

If this is a feature request, please review our contribution guidelines.

[alpozcan]

I have mentioned the same thing in #2833 (comment)

[alpozcan]

sorry for the misunderstanding regarding the dind side-container. Closing