This message was deleted.

Use k3d managed registry, and when building your docker images - push them there. No need to import.

thanks, basically I want to use images from docker hub, either k3d or local docker registry requires me to re-tag the image 😅

why ???

based on user repro steps I deploy a specific version of the operator inside k3d and most of the times I'll have those images available in local docker cache. so I want k3d (basically cri-o) to look my cache rather than hitting docker hub

Did you check this ? https://github.com/k3d-io/k3d/releases/tag/v5.4.3

no, thanks for the pointer. It seems I'm using quite an old version. will take a look.

Thanks for chiming in here @millions-alarm-86298! @big-librarian-12753 unfortunately, containerd cannot make any use of the docker image cache. There's an issue open for years now for docker to move to the containerd variant, but afaik that didn't happen yet.