I’m trying to deploy a very simple container (from a Dockerfile) but the Pod crashed at launch time. When I go to “Live logs”, the logs don’t load and I have an infinite loading (never resulting)
can you help me to know what’s going on?
Dockerfile
FROM alpine:3.17.3
RUN apk add --no-cache postgresql-client redis
ENTRYPOINT ["/bin/sh"]
Hi @clemg ,
Your app fails to start because you didn’t define the CMD command to be executed. You can directly set this CMD command via the Qovery interface or inside your Dockerfile.
Unfortunately, I still have the same issue after adding RUN /bin/sh in my Dockerfile or ["bin", "sh"] in the Qovery interface.
Note that when I build the image and run it on my machine, the container works as expected
How do you validate that it works on your local machine?
docker build -t test .
docker run -t test
Hi @clemg , actually, you are just opening a shell inside your container.
/t/test $ docker build -t test .
[+] Building 3.1s (6/6) FINISHED
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 129B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for docker.io/library/alpine:3.17.3 2.0s
=> [1/2] FROM docker.io/library/alpine:3.17.3@sha256:124c7d2707904eea7431fffe91522a01e5a861a624ee31d03372cc1d138a3126 0.0s
=> => resolve docker.io/library/alpine:3.17.3@sha256:124c7d2707904eea7431fffe91522a01e5a861a624ee31d03372cc1d138a3126 0.0s
=> => sha256:124c7d2707904eea7431fffe91522a01e5a861a624ee31d03372cc1d138a3126 1.64kB / 1.64kB 0.0s
=> => sha256:b5a5b7ce4eabc8414bf367761a28f4e8b16952ce5de537c15ed917b71b245f11 528B / 528B 0.0s
=> => sha256:51e60588ff2cd9f45792b23de89bfface0a7fbd711d17c5f5ce900a4f6b16260 1.49kB / 1.49kB 0.0s
=> [2/2] RUN apk add --no-cache postgresql-client redis 0.9s
=> exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:0700187871b487e0768f19ee1b26330924c14a1834e917f0d528a0067cb96c8c 0.0s
=> => naming to docker.io/library/test 0.0s
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
/t/test $ docker run -t test
/ #
You must provide a command to run. You can’t open a shell on a container via Qovery. Can you explain what you try to achieve with this container?
Ok, I see. I’m trying to have a simple “tooling” instance on my cluster to be able to access resources in the related VPC (databases, etc). From my understanding, I could use the qovery shell command to connect to it
Hi @clemg , you need to make your instance a long-running process. You can add inside your Dockerfile something keeping your container running as explained in this StackOverflow thread.