Please add a flag to avoid adding this "localhost/" prefix when tagging development images

[sebastian-philipp]

Feature request description

Hi there,

I'm coming from podman-desktop/extension-minikube#347

Essentially, I cannot make use of the local development image tagged by podman (MacOS + podman-desktiop + minkube):

• I can't push the image to minikube, as minikube load fails with: unable to calculate manifest: Error response from daemon: docker.io/localhost/controller:latest
• Even if I manage to push the image, then I'm getting an ImageInspectError: Failed to inspect image "controller:latest"

It seems as if the idea of adding a localhost/ prefix to development images is a good idea in theory, but neither minikube nor cri-o can handle this properly.

Please give me a way to avoid this and let me just use the image tag I specify without modifying it.

Thank you.

[afbjorklund]

Here is the code in Kubernetes, that adds the default registry:

https://github.com/kubernetes/kubernetes/blob/master/pkg/util/parsers/parsers.go

It uses the docker registry ("distribution") code, to "normalize":

https://github.com/distribution/reference/blob/main/normalize.go

[afbjorklund]

As a party trick, you can see what podman itself thinks about it:

podman pull localhost/myimage

Error: initializing source docker://localhost/myimage:latest: pinging container registry localhost: Get "https://localhost/v2/": dial tcp 127.0.0.1:443: connect: connection refused

If you want a real local registry, you could use e.g. localhost:5000

https://distribution.github.io/distribution/ (registry v2)

https://github.com/opencontainers/distribution-spec

[sebastian-pf9]

Right this whole thing doesn't work. I ended up using a fake name (e.g. podman build -t docker.io/something/image:latest) on docker.io just to get it working for me.

[afbjorklund]

BTW. Note that the only reason that localhost:5000 "works", is that a http proxy is being deployed:

https://minikube.sigs.k8s.io/docs/handbook/pushing/#4-pushing-to-an-in-cluster-using-registry-addon

kubernetes/cluster/addons/registry/README.md (it was abandoned and removed in 2018 / k8s 1.10)

The main reason to not deploy a real https registry, is because then you have to do certs and stuff...

[afbjorklund]

I ended up using a fake name (e.g. podman build -t docker.io/something/image:latest) on docker.io

If it makes you feel better you can use quay.io here instead (like using Containerfile for your Dockerfile)

[allanrogerr]

Please fix. It would be convenient not to have to rename everything.

[sebastian-philipp]

For me, this problem went away after a few days into the project after we had a proper name for the image.