Railway•2mo ago

Deployment stuck on "creating containers"

684d1eeb-55e6-4949-a8bf-85fc5143e0a4

Solution:

go ahead and duplicate the service then

Jump to solution

13 Replies

Percy•2mo ago

Project ID: 684d1eeb-55e6-4949-a8bf-85fc5143e0a4

JoëlOP•2mo ago

Deploying a KeystoneJS project, I managed to deploy it one time succesfully after that all deployed ments were unsuccesfull where the deploy step would just not start Tried bot the v1 and v2 build environments Looks like it gets stuck on trying to start the built docker container?

docker run -it us-west1.registry.rlwy.net/114d93fc-3f58-4649-9ec5-e0a1a5a9aac0:e5e9f9a7-0d97-4b83-a81c-5c1962453183

docker run -it us-west1.registry.rlwy.net/114d93fc-3f58-4649-9ec5-e0a1a5a9aac0:e5e9f9a7-0d97-4b83-a81c-5c1962453183

Tried to run this locally (dont know if that should work). But it did not Error:

request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).

request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).

Brody•2mo ago

thats a private registry and can only be accessed by railway's runners

JoëlOP•2mo ago

Ah okay, still the private runner doesnt seem to be able to access it some way as well Tail of the build logs:

Args: [-ol pipefail -c printf '\nPATH=/app/node_modules/.bin:$PATH' >> /root/.profile]

Running: [/bin/bash -ol pipefail -c printf '\nPATH=/app/node_modules/.bin:$PATH' >> /root/.profile]

Pushing layer us-west1.registry.rlwy.net/114d93fc-3f58-4649-9ec5-e0a1a5a9aac0/cache:cd9b8aa29e0c2549fc141022a1295cd673e4a99257c40835d00e570df04c5c91 to cache now

Pushing image to us-west1.registry.rlwy.net/114d93fc-3f58-4649-9ec5-e0a1a5a9aac0/cache:cd9b8aa29e0c2549fc141022a1295cd673e4a99257c40835d00e570df04c5c91

Taking snapshot of full filesystem...

Pushing layer us-west1.registry.rlwy.net/114d93fc-3f58-4649-9ec5-e0a1a5a9aac0/cache:8ca7d3c06da685c19799b225d03649b3ca798a11f75d7435b7974f75111ddff2 to cache now

Pushing image to us-west1.registry.rlwy.net/114d93fc-3f58-4649-9ec5-e0a1a5a9aac0/cache:8ca7d3c06da685c19799b225d03649b3ca798a11f75d7435b7974f75111ddff2

COPY . /app

Taking snapshot of files...

CMD ["yarn run start"]

Pushed us-west1.registry.rlwy.net/114d93fc-3f58-4649-9ec5-e0a1a5a9aac0/cache@sha256:2079d6c0d1cb9e60b797541014872d638a7a7cf4c55a3b3e7feba2bc4958b8cb

No files changed in this command, skipping snapshotting.

Pushed us-west1.registry.rlwy.net/114d93fc-3f58-4649-9ec5-e0a1a5a9aac0/cache@sha256:fd2a7041a050174c2bf09d81d8333d1934b01855073e37ea6e7d4fdbdb65b5e4

Pushing image to us-west1.registry.rlwy.net/114d93fc-3f58-4649-9ec5-e0a1a5a9aac0:293b8602-c4d0-40d9-8514-3afd442764af

container event container died

Stopping Container

Pushed us-west1.registry.rlwy.net/114d93fc-3f58-4649-9ec5-e0a1a5a9aac0@sha256:7597c410f25b1e6b2f67e13a425ac07bd07fca7f46a428a147e3fe4405592c3f

Args: [-ol pipefail -c printf '\nPATH=/app/node_modules/.bin:$PATH' >> /root/.profile]

Running: [/bin/bash -ol pipefail -c printf '\nPATH=/app/node_modules/.bin:$PATH' >> /root/.profile]

Pushing layer us-west1.registry.rlwy.net/114d93fc-3f58-4649-9ec5-e0a1a5a9aac0/cache:cd9b8aa29e0c2549fc141022a1295cd673e4a99257c40835d00e570df04c5c91 to cache now

Pushing image to us-west1.registry.rlwy.net/114d93fc-3f58-4649-9ec5-e0a1a5a9aac0/cache:cd9b8aa29e0c2549fc141022a1295cd673e4a99257c40835d00e570df04c5c91

Taking snapshot of full filesystem...

Pushing layer us-west1.registry.rlwy.net/114d93fc-3f58-4649-9ec5-e0a1a5a9aac0/cache:8ca7d3c06da685c19799b225d03649b3ca798a11f75d7435b7974f75111ddff2 to cache now

Pushing image to us-west1.registry.rlwy.net/114d93fc-3f58-4649-9ec5-e0a1a5a9aac0/cache:8ca7d3c06da685c19799b225d03649b3ca798a11f75d7435b7974f75111ddff2

COPY . /app

Taking snapshot of files...

CMD ["yarn run start"]

Pushed us-west1.registry.rlwy.net/114d93fc-3f58-4649-9ec5-e0a1a5a9aac0/cache@sha256:2079d6c0d1cb9e60b797541014872d638a7a7cf4c55a3b3e7feba2bc4958b8cb

No files changed in this command, skipping snapshotting.

Pushed us-west1.registry.rlwy.net/114d93fc-3f58-4649-9ec5-e0a1a5a9aac0/cache@sha256:fd2a7041a050174c2bf09d81d8333d1934b01855073e37ea6e7d4fdbdb65b5e4

Pushing image to us-west1.registry.rlwy.net/114d93fc-3f58-4649-9ec5-e0a1a5a9aac0:293b8602-c4d0-40d9-8514-3afd442764af

container event container died

Stopping Container

Pushed us-west1.registry.rlwy.net/114d93fc-3f58-4649-9ec5-e0a1a5a9aac0@sha256:7597c410f25b1e6b2f67e13a425ac07bd07fca7f46a428a147e3fe4405592c3f

Deploy logs:

*void*

*void*

Brody•2mo ago

failed 5 days ago, have you since tried to redeploy?

JoëlOP•2mo ago

Yes that is incorrect Tried 5 times again totday Waited a couple days to see it was a temp issue I think it bugged out or reset or something

Brody•2mo ago

mind if i try?

JoëlOP•2mo ago

Sure

Brody•2mo ago

is there any data in the volume?

JoëlOP•2mo ago

Nope Not important Everything is blank

Solution

Brody•2mo ago

go ahead and duplicate the service then

JoëlOP•2mo ago

Duplicating and deploying again worked Thanks

Brody•2mo ago

no problem, if this happens again let us know!

Gaming

Programming

Deployment stuck on "creating containers"