R
Railway•8mo ago
BruceX

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
Percy•8mo ago
Project ID: 11039c5b-a8e3-4789-ad66-c7c5ed7f843e
BruceX
BruceX•8mo 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
Hugo Tessera•8mo ago
Hello same issue for me!
Smack | DM FOR NODE RENT
Smack | DM FOR NODE RENT•8mo ago
Same issue here. They seem to have deployment issues right now which is likely the reason we get this error.
Brody
Brody•8mo ago
#🚨｜incidents
BruceX
BruceX•8mo ago
yes, I just found that. sorry.
Brody
Brody•8mo ago
this was resolved, closing out salute
Want results from more Discord servers?
Add your server
More Posts
It seems my ISP is blocking my access to Railway servicesHello, guys! I was trying to submit a project to Railway as usual. I just changed to one of the mostApplication failed to respondProject ID: a3d02844-50cd-462d-b23f-b6025e43fe69 I am trying to deploy Angular app on railway. ThaRailway is charging more (2x!) than the invoice totalHello, I tried to pay my invoice ($12,46) but the card has been refused because of insufficient funddeployment spend too long timedeployment spend too long time, it seems going to idle forever.Enabling bun on shared monorepo (turborepo) when using npm as package manager?Hi all! I use NPM as my package manager for my shared monorepo (turborepo), and because of that I doDeployment Failed during build processProject Id: 0c7fec98-322c-4deb-ac9d-d61c6c0278bf With no issues I have been deploying to Railway, Simple Webserver not respondingI tried making a simple webserver with Go and HTMX but it seems like it's not working, any idea whati need help with cors in spring bootI'm having trouble consuming an api hosted with mysqlhi , my name is marcos , i m having trouble cosuming an apihas taken too long to respond.Hi. I just uploaded my Monorepo and it's working good on logs. But when I try to access to: https://