[ENHANCEMENT] Ease using a private registry about k3d HOT 6 CLOSED

@d11wtq the k3s image that we use, doesn't work with the --docker flag, so that won't work unfortunately.
Instead of running a registry, you can use the import-images command to import pre-built images from your docker daemon into k3d.
Unfortunately, docker is using a different image storage format than containerd, so we cannot simply mount the image cache into k3d.

from k3d.

This feature is a must have!

from k3d.

+1 for this

from k3d.

Yeah I want to use k3d as an alternative to minikube, where you can docker build an image within minikube (via minikube docker-env) and Kubernetes can run that image because it's already present. Doesn't seem to be a way to get this working with k3d and Docker for Mac right now, aside from running a registry as detailed above? I tried using --server-arg --docker and mounting /var/run/docker.sock, but k3d then fails to create pods with Failed create pod sandbox: rpc error: code = Unknown desc = rewrite resolv.conf failed for pod ....

from k3d.

The very best news for us would be the success of this: moby/moby#38043
Making docker to use the containerd storage backend 👍
We could as well try to include something like BuildKit in k3d, which we could use for building inside k3d using e.g. k3d build image. Would require a shared caching/storage layer though to avoid having to build large images in each k3d node.

from k3d.

Closed via #161 and follow-up changes

from k3d.