Skip to content
GitHub deployment builds successfully but fails at CREATE_CONTAINER with no runtime logs
mauricerm
OP

9 days ago

Hi! I’m testing Railway and need help with a persistent container creation failure.

The application uses Python and SQLite, with a persistent volume mounted at /data. It deploys from a private GitHub repository using a Dockerfile.

What happens:

  • The build completes successfully in approximately 12 seconds.
  • Deployment remains at CREATE_CONTAINER for around 26 minutes.
  • It eventually fails with “An unknown error occurred.”
  • No application startup or runtime logs appear.

We previously delivered the application code through environment variables. We have since replaced that setup with a conventional GitHub/Dockerfile deployment and the start command ./deploy/start.sh, but the failure persists.

Details:

  • Service: mandaditos-web
  • Environment: preview
  • Region: sfo
  • Deployment ID: f9f3491b-56bc-470e-b9c7-8813b5483ea9
  • The persistent volume reports ready and has available space.
  • The trial account still has credit remaining.

Previous unresolved support thread:

https://station.railway.com/support/create-container-fails-with-failed-to-c-7487fa2a

Has anyone encountered this behavior? What additional information or checks would help identify why container creation fails before the application starts?

We need to preserve the existing /data volume and its contents. Thanks for any guidance!

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • 9 days ago


9 days ago

The issues preventing containers from starting have now been resolved. Our infrastructure engineers have been working continuously to restore affected services, and we’re extremely sorry for how long recovery has taken.

Some services may still need a redeploy to come back online. If your service is still unavailable, please cancel any pending deployments, then press Cmd+K or Ctrl+K and select Redeploy source image from the command palette.

Again, we’re extremely sorry for the disruption and for how long this has taken.


Status changed to Awaiting User Response Railway • 9 days ago


Status changed to Solved mauricerm • 5 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...