Seeing failures in deploying saying container shut down, but cannot find the container logs.

Need help figuring out how to debug this issue with deploying to prod. From my end I don't think the container should be failing like that, but can't figure out where the logs are. Here is the link to the deploy: https://railway.app/project/dfb66ac0-d8a1-48a6-b9d2-5941065b6a8a/service/2c9e540d-f74a-4320-a62e-8c2ae0d1137e?id=01fefde6-1a8d-4be4-ba41-6d8f17b9404b
Railway
404 - Page not found
Railway is an infrastructure platform where you can provision infrastructure, develop with that infrastructure locally, and then deploy to the cloud.
7 Replies
Percy
Percy10mo ago
Project ID: dfb66ac0-d8a1-48a6-b9d2-5941065b6a8a,2c9e540d-f74a-4320-a62e-8c2ae0d1137e,01fefde6-1a8d-4be4-ba41-6d8f17b9404b
anshulaggy
anshulaggy10mo ago
Hmm the error I keep seeing is Error response from daemon: manifest for registry.rlwy.net/2c9e540d-f74a-4320-a62e-8c2ae0d1137e:01fefde6-1a8d-4be4-ba41-6d8f17b9404b not found: manifest unknown: manifest unknown which seems to be a problem a few other folks are having. Aditionally from looking at the docs provided it doesn't really explain how to look at the registry to see why the container failed to build From the end of the Build Logs:
The push refers to repository [registry.rlwy.net/2c9e540d-f74a-4320-a62e-8c2ae0d1137e]



Publish time: 0.02 seconds



=========================

Container failed to start

=========================



Error response from daemon: manifest for registry.rlwy.net/2c9e540d-f74a-4320-a62e-8c2ae0d1137e:01fefde6-1a8d-4be4-ba41-6d8f17b9404b not found: manifest unknown: manifest unknown
The push refers to repository [registry.rlwy.net/2c9e540d-f74a-4320-a62e-8c2ae0d1137e]



Publish time: 0.02 seconds



=========================

Container failed to start

=========================



Error response from daemon: manifest for registry.rlwy.net/2c9e540d-f74a-4320-a62e-8c2ae0d1137e:01fefde6-1a8d-4be4-ba41-6d8f17b9404b not found: manifest unknown: manifest unknown
Brody
Brody10mo ago
will bring this up to the team
anshulaggy
anshulaggy10mo ago
thank you Brody!
aaron
aaron10mo ago
We're seeing the same error on our deployment.
nickmacavoy
nickmacavoy10mo ago
Fixed now for me