ko support podman(cri-o)

[jwcesign]

Environment

k8s with cri-o container engine

what problem

If with env KO_DOCKER_REPO=ko.local, the build img only can be found with docker.
When the pod is launched, there will be a error:img pull failed

what need

ko support podman

[jwcesign]

cc @dprotaso @mattmoor @imjasonh

[imjasonh]

ko uses go-containerregistry's pkg/v1/daemon.Write to load built images into the Docker daemon, which internally uses docker/client.Client.ImageLoad

Is there an equivalent for Podman? Or is there some way to configure Podman to accept images in the same way as daemon.Write?

There was some discussion in go-containerregistry about supporting Podman better, maybe that's a place to start: google/go-containerregistry#998

[jwcesign]

Let me check.
LIke what said in google/go-containerregistry#998, it needs to run podman server with root.
Now I work like follows:

sudo podman system service -t 5000 &
export DOCKER_HOST=unix:///run/podman/podman.sock
export KO_DOCKER_REPO=ko.local

[imjasonh]

Thanks for figuring that out. We should probably document this somewhere more visible... 🤔