Deployment stuck at CREATE_CONTAINER — needs infra-level cleanup of stuck container namespace Service: striking-intuition (project ocean-property, environment production, region US West / sfo, Hobby plan). My service has failed EVERY deployment for ~16 hours. Your own Railway Agent investigated and found: - The deployment is stuck in a PENDING CREATE_CONTAINER state. The build succeeds (SNAPSHOT_CODE completes), but the container never starts — only a "Stopping Container" log appears ~19 minutes later. - A fresh deployment triggered by your Agent (dec6e2da) stalled AGAIN at CREATE_CONTAINER. - The Agent concluded this is a service-specific infrastructure state (it confirmed NO platform-wide incident), and that it likely needs Railway support to FORCE-CLEANUP the stuck container namespace / volume mount. I have already ruled out everything on my side: - Rollback to a previously-working image (usePreviousImageTag) — fails identically. - Detaching/reattaching the volume — no change (volume shows Ready). - Disconnecting the GitHub source — no change. - railway up, redeploy, rollback, from-source — all fail identically. This started right after a `railway up` deploy ~16 hours ago. Please force-cleanup the stuck container/namespace for this service so it can deploy again. Failed deployment IDs: 5723729d-be5a-4e65-a109-9b31d955c33b 30aa14cd-c2d0-4aca-ad4c-5d769099386c dec6e2da-8f57-4b69-9c4e-21cbe5922a9e

Deployment stuck at CREATE_CONTAINER — needs infra cleanup (Railway Agent confirmed)

annavostok

HOBBYOP

12 days ago

Deployment stuck at CREATE_CONTAINER — needs infra-level cleanup of stuck container namespace

Service: striking-intuition (project ocean-property, environment production, region US West / sfo, Hobby plan).

My service has failed EVERY deployment for ~16 hours. Your own Railway Agent investigated and found:

The deployment is stuck in a PENDING CREATE_CONTAINER state. The build succeeds (SNAPSHOT_CODE completes), but the container never starts — only a "Stopping Container" log appears ~19 minutes later.
A fresh deployment triggered by your Agent (dec6e2da) stalled AGAIN at CREATE_CONTAINER.
The Agent concluded this is a service-specific infrastructure state (it confirmed NO platform-wide incident), and that it likely needs Railway support to FORCE-CLEANUP the stuck container namespace / volume mount.

I have already ruled out everything on my side:

Rollback to a previously-working image (usePreviousImageTag) — fails identically.
Detaching/reattaching the volume — no change (volume shows Ready).
Disconnecting the GitHub source — no change.
railway up, redeploy, rollback, from-source — all fail identically.

This started right after a railway up deploy ~16 hours ago. Please force-cleanup the stuck container/namespace for this service so it can deploy again.

Failed deployment IDs:

5723729d-be5a-4e65-a109-9b31d955c33b

30aa14cd-c2d0-4aca-ad4c-5d769099386c

dec6e2da-8f57-4b69-9c4e-21cbe5922a9e

Awaiting User Response

2 Replies

Status changed to Awaiting Railway Response Railway • 12 days ago

chandrika

EMPLOYEE

12 days ago

Your previous container has not shut down on our side, and while it is still

running, a new deployment cannot take over from it. That is why every build

completes and then stalls at container creation, and why the rollback, the

source disconnect, and the repeated redeploys all ended the same way. You

have already ruled out everything on your side correctly. We are clearing the

stuck container from our side and will confirm here once your service can

deploy again.

Status changed to Awaiting User Response Railway • 12 days ago

noahd

EMPLOYEE

10 days ago

Hey! Looked into things on our end here.

As it was labeled "do not touch" can you open the deployment, hit the 3 dots next to "remove deployment" then press cmd + k and "deploy latest commit"? Should put it back into a better state.

Welcome!