Cannot run container after build

[huonguyenlt]

Summary

I am trying to build and run docker image using podman. I followed instruction here https://eclipse.dev/che/docs/stable/end-user-guide/running-containers-with-kubedock/
Base on the document, it say I have to build image, push image then run image.
However, only success on build step. Push and run steps are failed.
Dockerfile

FROM alpine:latest
CMD ["echo", "Hello, Docker!"]

podman build -t test .

STEP 1/2: FROM alpine:latest
Resolved "alpine" as an alias (/etc/containers/registries.conf.d/000-shortnames.conf)
Trying to pull docker.io/library/alpine:latest...
Getting image source signatures
Copying blob da9db072f522 done  
Copying config 63b790fccc done  
Writing manifest to image destination
STEP 2/2: CMD ["echo", "Hello, Docker!"]
COMMIT test
--> 1b4946eb5522
Successfully tagged localhost/test:latest
1b4946eb55225aeab3cba27564696618db8e4bc2ab49d75f025cc0f91b48

podman push localhost/test:latest

Getting image source signatures
WARN[0000] Failed, retrying in 1s ... (1/3). Error: trying to reuse blob sha256:75654b8eeebd3beae97271a102f57cdeb794cc91e442648544963a7e951e9558 at destination: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused 
Getting image source signatures
WARN[0001] Failed, retrying in 1s ... (2/3). Error: trying to reuse blob sha256:75654b8eeebd3beae97271a102f57cdeb794cc91e442648544963a7e951e9558 at destination: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused 
Getting image source signatures
WARN[0002] Failed, retrying in 1s ... (3/3). Error: trying to reuse blob sha256:75654b8eeebd3beae97271a102f57cdeb794cc91e442648544963a7e951e9558 at destination: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection refused 
Getting image source signatures
Error: trying to reuse blob sha256:75654b8eeebd3beae97271a102f57cdeb794cc91e442648544963a7e951e9558 at destination: pinging container registry localhost: Get "https://localhost/v2/": dial tcp [::1]:443: connect: connection ref

$ podman run localhost/test:latest

Error: failed to start container; error pulling image

Here is part of my devfile.yml

env:
        - name: KUBEDOCK_PARAMS
          value: "--reverse-proxy --kubeconfig /home/user/.kube/config --initimage quay.io/agiertli/kubedock:0.13.0"
        - name: KUBEDOCK_ENABLED
          value: 'true'
        - name: DOCKER_HOST
          value: 'tcp://127.0.0.1:2475'
        - name: TESTCONTAINERS_RYUK_DISABLED
          value: 'true'
        - name: TESTCONTAINERS_CHECKS_DISABLE
          value: 'true'
      endpoints:
        - exposure: none
          name: kubedock
          protocol: tcp
          targetPort: 2475
        - exposure: public
          name: http-booster
          protocol: http
          targetPort: 8080
          attributes:
            discoverable: true
            urlRewriteSupported: tr

Please give advice on what I did wrong. The eclipse-che is deployed on my kubernetes cluster (EKS), not openshift.

Relevant information

No response

[ibuziuk]

@huonguyenlt hello, it looks like the main problem is that you can not push to the internal registry, right?
https://localhost/v2/": dial tcp [::1]:443: connect: connection refused

[huonguyenlt]

@ibuziuk I think so. Can you suggest what I should do here?

[huonguyenlt]

Can i just run the container without pushing it to internal registry?

[huonguyenlt]

When build the image, podman automatically add registry localhost to the image name. But there is no localhost registry

[ibuziuk]

@huonguyenlt have you tried tagging the image and pushing the image to some external registry e.g. https://quay.io/ ?

[huonguyenlt]

@ibuziuk no I did not.After building image, podman auto add localhost registry. Do I have to push it to some external registry to use it?