Docker image builds but stalls on deploy with no error
Previous attempts to build would go on for over 10 minutes after the container was built and then eventually time out.
Now the container shows as built but the deployment status just says
Waiting
In both cases, no logs are displayed in Deploy Logs, Only the message:
No deployment logs. All output sent to stdout will be displayed hereProject ID: 855986b0-ece5-4720-97b2-572a841362de
29 Replies
Project ID:
855986b0-ece5-4720-97b2-572a841362dewhat is the source of this service
Github
Its a python application, hosted on github, deployed via a Dockerfile
send the dockerfile please
And here is the last deploy id in case its useful:
7b9357b1-f5bc-477c-963f-51d44c642f9d
these are multiple dockerfiles right
No, that is a single Dockerfile.
By default the last stage is targeted which is called runner.
The previous stages are only targeted by other tools for use with devcontainers, and integration tests.
But the Dockerfile hasn't changed since the previous working deployment which was earlier today.
wdym targeted, how would you be telling railway what stage to run
Its a multi stage build file with multiple targets.
By default, a Dockerfile runs to the bottom so railway would use the stage at the bottom.
But when using tools e.g. docker compose, you can explicitly target an intermediate stage and run the container from there.
https://docs.docker.com/build/building/multi-stage/#stop-at-a-specific-build-stage
Docker Documentation
Multi-stage builds
Learn about multi-stage builds and how you can use
them to improve your builds and get smaller images
try a simpler dockerfile
Same results. It builds and then nothing happens.
Doesn't show any signs of it attempting to run - no logs from the Deploy logs
what about the build logs?
The build logs look fine.
In the list of deployments, the status just says "Waiting"
your build logs are cut off, use this https://bookmarklets.up.railway.app/log-downloader/
and now its just saying "waiting" correct?
Yes.
Before that, it would say deploying but go on from anywhere between 10 up to 50 minutes.
But in both cases, no logs would appear in the deploy logs
@thomas yeah something is for sure wrong with railway
We have created a new branch on github at the last commit that deployed successfully, and pointed the railway project to that new branch.
Even that did not deploy.
okay let's wait for thomas
Weird looking into this now, for my reference are you guys all on a team? There is no wide spread issue with the builder that we know of just yet so I am trying to figure out a root cause
Can you pin a list of these hacked in features for me sometime Brody. I am just interested to see what you built because we didn't yet haha
I don't know the other posted who opened a similar thread -- I only replied there because it seemed like we were facing the same issue.
good to know
We are looking into this further, it does not appear to be wide spread but it is on our side.
We are experiencing an issue that is affecting a small number of users. The team is working on it.
We have created an incident you can subscribe to here for updates on when services for you will be restored https://railway.instatus.com/clnp2ir5l43412bfn1q83e0bbn
I don't think we actually have anything of value in the volume but we do need a volume.
If we removed the volume and recreated it, would that unblock it?
no, that isn't very likely, the underlying infrastructure is giving us errors.
@aaron Can you please kick off another deploy
Its working 🥳
There are still no logs showing in deploy logs though
should be back now 🙂
Great! Thanks for your help getting it resolved