Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot run container after build #23265

Open
huonguyenlt opened this issue Nov 25, 2024 · 1 comment
Open

Cannot run container after build #23265

huonguyenlt opened this issue Nov 25, 2024 · 1 comment
Labels
area/udi Issues and PRs related to the universal developer image https://github.com/devfile/developer-images kind/question Questions that haven't been identified as being feature requests or bugs. severity/P2 Has a minor but important impact to the usage or development of the system. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach

Comments

@huonguyenlt
Copy link

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

@huonguyenlt huonguyenlt added the kind/question Questions that haven't been identified as being feature requests or bugs. label Nov 25, 2024
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Nov 25, 2024
@ibuziuk ibuziuk added the severity/P2 Has a minor but important impact to the usage or development of the system. label Nov 25, 2024
@ibuziuk
Copy link
Member

ibuziuk commented Nov 25, 2024

@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

@ibuziuk ibuziuk added area/udi Issues and PRs related to the universal developer image https://github.com/devfile/developer-images status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/udi Issues and PRs related to the universal developer image https://github.com/devfile/developer-images kind/question Questions that haven't been identified as being feature requests or bugs. severity/P2 Has a minor but important impact to the usage or development of the system. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach
Projects
None yet
Development

No branches or pull requests

3 participants