a month ago
Project: foreclosure-scraper / production
Both services failing at "Deploy → Create container" with "Failed to
create deployment" and zero deploy logs after build success.
Latest failed deployment IDs:
dashboard: fc45ea21-622c-4f1e-8bb9-3b84a30610d4
scraper-cron: 7face5c3-d87c-4608-8aab-298698de6961
Reproduced via:
- GitHub auto-deploy (multiple commits)
- railway redeploy
- railway up from CLI
- Region migration us-west2 → us-east4 (no change in symptom)
Pre-deploy step succeeds (~7s) but production "Create container"
step fails immediately with no stdout. railway logs --deployment
returns empty for all failed IDs.
All env vars verified present. Status page green throughout.
Please investigate scheduler / volume state for this project.
2 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Update with definitive evidence:
Replaced Dockerfile CMD with literally:
CMD ["sh", "-c", "echo HELLO_FROM_CONTAINER && sleep 3600"]
This is a hello-world that cannot crash.
Result: identical failure.
Deployment ID: f303e3da-2d80-4323-8ab7-9a27cd24d45b
Build: SUCCESS
Image: pushed (sha256:958b2689b8f42c44168b8e6c535082377ca5eb508de1bdb095d06273b12e8f92)
Deploy → Create container: FAILED, "Failed to create deployment"
Deploy logs: empty (HELLO_FROM_CONTAINER never printed)
This proves the issue is 100% in Railway's container runtime/
scheduler for this project — not in our code, image, or config.
There is no way echo + sleep can fail in user space.
Have already tried (none fixed it):
- Region migration us-west2 → us-east4
- Replica Limits 8/8 → 2/2
- GitHub auto-deploy, railway redeploy, railway up via CLI
- Container restart, all redeploys
Please manually unstick this project's scheduler/container slot.
The previous Apr 30 SUCCESS deploy (c4e229ff) is still serving
traffic on the dashboard service — the project isn't fully dead,
just unable to accept new container creations.
a month ago
Your last deployment attempt was May 4. Just redeploy and you should be good.
Status changed to Awaiting User Response Railway • about 1 month ago
23 days 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 • 23 days ago