Push image failed "connection refused" to openshift local from podman

[dfollereau]

Hello,
Pushing local podman image to openshift local (crc), it does not work with the latest version downloaded.

Error and How to reproduce (run on MacBook Pro M1 pro Apple Silicom CPU):
crc version
CRC version: 2.35.0+3956e8
OpenShift version: 4.15.10
Podman version: 4.4.4
Note: podman version is now quite old, 1 year old. It could be the issue with a recent podman version installed to pull the image.

Scenario to reproduce:
crc start
eval $(crc oc-env)
oc login -u kubeadmin -p xxxxx-xxxxx-xxxxx-xxxxx https://api.crc.testing:6443/
oc new-project demo
podman login -u kubeadmin -p $(oc whoami -t) default-route-openshift-image-registry.apps-crc.testing --tls-verify=false
podman pull quay.io/libpod/alpine
podman tag alpine:latest default-route-openshift-image-registry.apps-crc.testing/demo/alpine:latest

podman images
REPOSITORY TAG IMAGE ID CREATED SIZE
default-route-openshift-image-registry.apps-crc.testing/demo/alpine latest 915beeae4675 4 years ago 5.59 MB
quay.io/libpod/alpine

oc get is
No resources found in demo namespace.

podman push default-route-openshift-image-registry.apps-crc.testing/demo/alpine:latest --tls-verify=false
Getting image source signatures
Copying blob sha256:5e0d8111135538b8a86ce5fc969849efce16c455fd016bb3dc53131bcedc4da5
Getting image source signatures
Copying blob sha256:5e0d8111135538b8a86ce5fc969849efce16c455fd016bb3dc53131bcedc4da5
Getting image source signatures
Copying blob sha256:5e0d8111135538b8a86ce5fc969849efce16c455fd016bb3dc53131bcedc4da5
Getting image source signatures
Copying blob sha256:5e0d8111135538b8a86ce5fc969849efce16c455fd016bb3dc53131bcedc4da5

Error: trying to reuse blob sha256:5e0d8111135538b8a86ce5fc969849efce16c455fd016bb3dc53131bcedc4da5 at destination: pinging container registry default-route-openshift-image-registry.apps-crc.testing: Get "http://default-route-openshift-image-registry.apps-crc.testing/v2/": dial tcp 127.0.0.1:80: connect: connection refused

oc get is
No resources found in demo namespace.
No image pushed to openshift local to be used by our micro-services.

Why crc is embarking podman 4.4.4 version? Do you have an idea why connection refused?
Thanks
Denis

[praveenkumar]

Why crc is embarking podman 4.4.4 version? Do you have an idea why connection refused?

Ignore that, we are going to remove it soon.

Now to your issue, Are you trying to do that from a linux host or using mac/windows with podman desktop?

[praveenkumar]

Also check #3897 (comment) if you are using the Podman desktop.

[adrianriobo]

he is running no MacBook Pro M1 pro Apple Silicom CPU the pull push scenario has passed for 2.35.0 on all mac archs and OSs versions for us although we are testing it with registry.access.redhat.com/ubi8/httpd-24:latest

[dfollereau]

Hello, thanks for your answer I am going to double check the link you provided! I am using and my team too, Mac Apple Silicon M1 or M2 pro. This is for our localdev hence we use podman desktop and openshift local (crc)

[praveenkumar]

@adrianriobo in our testing we use podman from our crc instance not from the PD which @dfollereau is using so in his case #3897 (comment) is going to work.

[adrianriobo]

yeah exactly

[dfollereau]

I confirm this ticket/comment: #3897 (comment)
is fixing my issue.
May be the command "podman login -u kubeadmin -p $(oc whoami -t) default-route-openshift-image-registry.apps-crc.testing --tls-verify=false" should be reviewed to take better into account certificate to avoid the workaround going in the registry and force accepting. however this is on podman side and not crc, not in your basket if I understand well.
Thanks anyway for the help, have a good WE.