Deployment stuck on "creating containers"
joehoel
HOBBYOP

a year ago

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

24 Replies

joehoel
HOBBYOP

a year 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


joehoel
HOBBYOP

a year ago

Tried bot the v1 and v2 build environments


joehoel
HOBBYOP

a year ago

Looks like it gets stuck on trying to start the built docker container?


joehoel
HOBBYOP

a year ago

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


joehoel
HOBBYOP

a year ago

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


joehoel
HOBBYOP

a year ago

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


a year ago

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


joehoel
HOBBYOP

a year ago

Ah okay, still the private runner doesnt seem to be able to access it some way as well


joehoel
HOBBYOP

a year ago

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```


joehoel
HOBBYOP

a year ago

Deploy logs: *void*


a year ago

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


joehoel
HOBBYOP

a year ago

Yes that is incorrect


joehoel
HOBBYOP

a year ago

Tried 5 times again totday


joehoel
HOBBYOP

a year ago

Waited a couple days to see it was a temp issue


joehoel
HOBBYOP

a year ago

I think it bugged out or reset or something


a year ago

mind if i try?


joehoel
HOBBYOP

a year ago

Sure


a year ago

is there any data in the volume?


joehoel
HOBBYOP

a year ago

Nope


joehoel
HOBBYOP

a year ago

Not important


joehoel
HOBBYOP

a year ago

Everything is blank


a year ago

go ahead and duplicate the service then


joehoel
HOBBYOP

a year ago

Duplicating and deploying again worked


joehoel
HOBBYOP

a year ago

Thanks


Loading...