3 days ago
What's happening:
Every deployment fails immediately at CREATE_CONTAINER with "Failed to create deployment"
No logs are produced because the container never starts
The service config is correct: image is set, networking is configured, variables are in place
This points to an infrastructure issue on Railway's side, not your configuration
Next step: You'll need to contact Railway support with this information. They can investigate why container creatio
4 Replies
Status changed to Awaiting Railway Response Railway • 3 days ago
3 days ago
What you should report:
Service ID: 10cbd3af-4b69-4655-b828-04350833eadf
Deployment ID: 0f368d27-ac7f-4ac7-b03c-03d4e788fdd5
That all deployments fail at CREATE_CONTAINER with no logs
That the image is atendai/evolution-api:latest
Status changed to Awaiting Railway Response Railway • 3 days ago
3 days ago
??
19 hours ago
Your deployments are failing because the Docker image atendai/evolution-api:latest could not be pulled from Docker Hub. Your other two services in the same project (Postgres and n8n) deployed successfully, so this is specific to that image rather than a platform issue. We recommend posting in our community at https://station.railway.com/questions for help troubleshooting the image configuration.
Status changed to Awaiting User Response Railway • about 19 hours ago
19 hours ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 19 hours ago
19 hours ago
Hey! The image changed from atendai/evolution-api:latest to evoapicloud/evolution-api:latest, just change the source image and you're good to go.