Skip to content
Deployment stuck at "Creating containers" despite successful build and app startup
linzzeventsteam-bng
OP

2 months ago

My Spring Boot production deployment repeatedly gets stuck at "Creating containers..." for 10+ minutes.

Project: linzz-impressions

Service: ravishing-inspiration

Environment: production

Region: US East (Virginia, USA)

What I have verified:

  • Docker build completes successfully.
  • Maven package completes successfully.
  • Docker image is successfully created and published.
  • The application starts successfully when the container runs.
  • Spring Boot starts on port 8080.
  • MySQL connection succeeds.
  • JPA initializes successfully.
  • Tomcat starts successfully on port 8080.
  • No application exception is shown in the runtime logs.
  • Public networking is correctly configured for port 8080.
  • No Healthcheck Path is configured.
  • CPU and memory usage are not exhausted.
  • The service has a persistent volume mounted at /app/persist.
  • MySQL uses a separate mysql-volume.
  • The same issue occurs with both GitHub deployments and Railway CLI (railway up).

The runtime logs previously showed:

"Started LinzzImpressionApplication"

"Tomcat started on port 8080"

A previous deployment diagnosis also reported that the build finished and image was published, with no build or application error.

Please check whether container provisioning or persistent-volume mounting is causing the deployment to remain stuck at "Creating containers".

I do not want the existing application volume or MySQL volume deleted/recreated because they contain production data.

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • about 2 months ago


2 months ago

This has been resolved, and your service is back online.


Status changed to Awaiting User Response Railway • about 2 months ago


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...