Epic: Support the docker-cli to build and run container images

[jandubois]

This will require the following pieces

• Add moby to the alpine-lima ISO #808
• Add moby to the WSL distribution #809
• Add docker-cli to RD #810
• Launch dockerd on lima (listening on TCP) #869
• Ability to toggle between moby & nerdctl #900
• Implement socket forwarding from VM to host (implement in Lima for macOS) #811
  • Handle volumes & other file paths (@jandubois believes this works automatically, as long as directories are mounted)
• Implement socket forwarding for Windows ( to ) #812
  • Handle volumes & other file paths
• Configure k3s to (optionally) use the dockerd socket, so it can use images built by docker build #814
• Set external node IP on macOS #901
• Create/overwrite the docker.sock symlink on demand #939 - depends on 814
• Launch dockerd on WSL #950
  • Launch docker proxy for other WSL distributions (i.e. integrations). #1011

[mook-as]

Note that we'll also need to figure out what to do with volume mounts, because they're on different machines.

It's unclear if this task is supposed to cover Windows — that would include cross-distro volume mounts, which is More Fun.

[jandubois]

It's unclear if this task is supposed to cover Windows — that would include cross-distro volume mounts, which is More Fun.

Yes, it was supposed to cover Windows as well (that's why I didn't put the macOS label on it). And yes, we probably need to add a bunch more tasks to the checklist; this issue is supposed to be the umbrella bug to tie them all together.

[mook-as]

Adjusted the checklist to make it more explicit that Windows is covered.

[mook-as]

Removed #910 from the list because we won't need it for the first go (we'll just clobber the docker socket as appropriate).

[gaktive]

At this stage, the main feature work on this is done.

I'll close this, so bugs discovered around this will exist as new and likely separate tickets.

[xaocon]

Sorry to bump a closed issue but I'm just curious what the impetus was for this? Was nerdctl not a good replacement for docker in all cases?

[jandubois]

Was nerdctl not a good replacement for docker in all cases?

Yes, there are various features that are still unimplemented in nerdctl. I did a test of using alias docker=nerdctl and then trying to build various Github projects that use docker build in their Makefile. The nerdctl alias failed in more than 50% of the cases to build and run the project (very unscientific sampling, but still).

Of course the long term goal is to improve nerdctl to get feature-parity as much as possible, but it seemed not achievable in the short term.

Furthermore, some projects only work with the dockerd API and not with containerd. For us the most important one is k3d. We could only get it to work with Rancher Desktop if we at least optionally support using dockerd instead of containerd.