Railway•13mo ago

deployment build went wrong

After I pushed commits, and then github actions run without error, but the railway went wrong in the final step.

7 Replies

Percy•13mo ago

Project ID: 11039c5b-a8e3-4789-ad66-c7c5ed7f843e

BruceXOP•13mo ago

11039c5b-a8e3-4789-ad66-c7c5ed7f843e the build logs end with

Layer already exists  f360b0e17c4f
Layer already exists  f86de32951ed
Mounted from fbd2d651-174e-4000-bbae-3c03af257a88  d3de144c74a3
Pushing [==================================================>]  4.445MB e4203e75a23f
Pushing [==================================================>]  4.713MB e4203e75a23f
Layer already exists  dc0585a4b8b7
Mounted from 07e03da8-7aa7-4afe-a1cf-8ec2b836b069  b13b190b40d7
Pushed  e4203e75a23f
 
Publish time: 2.46 seconds
 
=========================
Container failed to start
=========================
 
Error response from daemon: manifest for us-west1.registry.rlwy.net/67cc532c-1fc7-4219-881f-4b08b37ab77b:331f47a7-b9eb-401e-811b-b24d3c1106ef not found: manifest unknown: manifest unknown

Layer already exists  f360b0e17c4f
Layer already exists  f86de32951ed
Mounted from fbd2d651-174e-4000-bbae-3c03af257a88  d3de144c74a3
Pushing [==================================================>]  4.445MB e4203e75a23f
Pushing [==================================================>]  4.713MB e4203e75a23f
Layer already exists  dc0585a4b8b7
Mounted from 07e03da8-7aa7-4afe-a1cf-8ec2b836b069  b13b190b40d7
Pushed  e4203e75a23f
 
Publish time: 2.46 seconds
 
=========================
Container failed to start
=========================
 
Error response from daemon: manifest for us-west1.registry.rlwy.net/67cc532c-1fc7-4219-881f-4b08b37ab77b:331f47a7-b9eb-401e-811b-b24d3c1106ef not found: manifest unknown: manifest unknown

Can somebody help me! pls! Another retry, build log end with :

Waiting  f86de32951ed
Waiting  b13b190b40d7
Waiting  dc0585a4b8b7
 
Publish time: 0.03 seconds
 
=========================
Container failed to start
=========================
 
activity StartToClose timeout

Waiting  f86de32951ed
Waiting  b13b190b40d7
Waiting  dc0585a4b8b7
 
Publish time: 0.03 seconds
 
=========================
Container failed to start
=========================
 
activity StartToClose timeout

Hugo Tessera•13mo ago

Hello same issue for me!

Smack | DM FOR NODE RENT•13mo ago

Same issue here. They seem to have deployment issues right now which is likely the reason we get this error.

Brody•13mo ago

#🚨｜incidents

BruceXOP•13mo ago

yes, I just found that. sorry.

Brody•13mo ago

this was resolved, closing out salute

Gaming

Programming

deployment build went wrong