I’m getting a deployment error and am at a loss on how to proceed. The first build succeeded but failed to start, probably because the env var scope was wrong (I had set them to Project instead of Environment). I fixed that, but the redeploy looks like it’s showing an old pod stuck in error state:
🛰 Job at new tag 7c8b0e64c628796beb3b7c0a35c899c7103f1d1b has 1 pods: 0 running, 0 starting, 0 terminating and 1 in error
...
❌ job failed !
Either it couldn't be executed correctly after `0` retries or its execution didn't finish after `5.00 minutes`.
Underlying error: `BackoffLimitExceeded: Job has reached the specified backoff limit`.
| 2023-09-12 23:22:04.373 | job-z08fcb5fe-tapi-hkvhx | exec /tini: no such file or directory
ERRO[2023-09-13T13:09:17-05:00] connection closed by server: websocket: close 1011 (internal server error): Remote closed stream
Relevant lines from Dockerfile:
# Add Tini
## https://github.com/krallin/tini#why-tini
ENV TINI_VERSION v0.19.0
ADD https://github.com/krallin/tini/releases/download/${TINI_VERSION}/tini /tini
RUN chmod +x /tini
ENTRYPOINT ["/tini", "--"]
# Start Server
CMD [ "npm", "start" ]
Why does tini fail to install? Is this the actual error or a symptom of a deeper issue?
Did your test have create-branch.sh to create the Neon branch? Could it be that the create script uses #!/bin/bash whereas the Dockerfile uses /bin/sh? The environment might not transfer from one to the other.
Switching Dockerfile to /bin/bash didn’t work, nor did changing create-branch.sh to use sh instead of bash`.
What finally worked was installing neonctl in create-branch.sh, allowing it to find neonctl:
yarn add global neonctl@v1.20.0
This has been a disappointing productivity drain the last few days. I would hope that a promoted feature such as Neon would get more attention, either with more thorough testing & debugging or more direct involvement assisting here.
Do you have some configuration in your repository that may interfer with yarn ?
Also, can you check if it fixes the issue to remove yarn -s prefix to call directly neonctl (without your previous fix to re-install neonctl) ? I’m pretty sure the neonctl is installed and available in your container.
At this point I’d expect to see my server startup logs. The only thing shown in the Live logs is:
Database: ps-dev
Shell script executed successfully with output values - check out your Qovery environment variables :)
Is that expected? I see the EC2 instance in AWS, but the response from that address is Nginx 404.
The deployment logs show the COPY and RUN commands in the Dockerfile, but no output for the commands after that.
# These lines are executed
COPY . ./
RUN npm install
RUN npm run build
# No indication that CMD is executed
EXPOSE 4000 80
ENTRYPOINT [ "/bin/sh" ]
# Start Server
CMD [ "npm", "start" ]
