Request: Support for k3s import

[dariusaurius]

Hi,

hope you could support k3s in the future. k3s comes with its own containerd.

ctr needs to be called with k3s in order to import the images, e.g. k3s ctr image import

Since k3s also supports an Air-Gapped installation, this would make a perfect duo 🙌

Kind regards

[jimmidyson]

Sounds great! Perhaps we can just check if k3s in PATH and run that when we do import? Fancy pushing a pr?

[dariusaurius]

Sorry for my late reply. I moved away from mindthegap because I noticed other incompatibilities that may come from using specific helm charts in our Harbor at my company. Since mindthegap does not export the repository, image name and tag information (or at least I was not able to configure mtg to do so), k3s reports an "ImagePullBackOff" because it is looking in containerd for this information to build the pod.

I created a bash script with a combination of "helm show" and "helm template" to extract this information and pipe it to "docker pull" and then to "docker save" to create tar balls for "k3s ctr image import". The downside to this are redundant fragments, but at least it works.

If you are interested in my solution, I could try to share it with you.

Regards