a month ago
Hi Railway team,
I'm experiencing a persistent infrastructure error when deploying a Docker image. The deployment fails at the CREATE_CONTAINER stage before any logs are produced.
Details:
- Image: evolutionapi/evolution-api:latest
- Deployment ID: 8d8a4ae5
- Plan: Hobby (just upgraded, issue persists)
- Regions tried: US West and US East — same error on both
- Error: "Failed to create deployment" — Diagnosis: Infrastructure Error
- The status page shows Fully Operational, so this appears to be an isolated issue
I've tried multiple redeploys with no success. This seems to be account or infrastructure-level, not a configuration issue.
Project: chic-friendship (e8f55880-0ab1-4891-b390-dad339de337e)
Service: evolution-api
Deployments failed:
- 60789b62-9203-4ddc-a2d1-8274b4421616 (sfo)
- 2d519550-5e86-46be-961e-1c47c6750c61 (sfo)
- 082516d7-fedc-4201-a57e-e838c7dc50be (iad)
Error: "Failed to create deployment" en CREATE_CONTAINER
Imagen: evolutionapi/evolution-api:latest
Tries regionsailed to create deployment: sfo, iad
Can you investigate? Thanks.
3 Replies
a month ago
We're aware of these transient build queue issues and are actively working on improvements.
Status changed to Awaiting User Response Railway • 27 days ago
Railway
We're aware of these transient build queue issues and are actively working on improvements.
a month ago
Ok thanks
Status changed to Awaiting Railway Response Railway • 27 days ago
a month ago
Your deployments are failing because the container image cannot be pulled from Docker Hub, not because of a platform or account problem. Each attempt to pull evolutionapi/evolution-api fails at the container creation step, and this has happened across the latest, 2.0.0, and 1.6.0 tags. Please confirm the image name and tag are correct and that the image is publicly available on Docker Hub. If the repository is private, add your registry credentials in the service's source settings so the pull can authenticate. Public Docker Hub images can also intermittently hit anonymous pull rate limits, so if the name and tag are correct, waiting a short time and redeploying may succeed. Pinning a specific version tag rather than latest tends to be more reliable.
Status changed to Awaiting User Response Railway • 27 days ago
20 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 • 20 days ago