a month ago
My service "Evolution-new" (Docker image atendai/evolution-api) has failed
at the container creation stage across 14 consecutive deploy attempts over
3 days, before any container starts.
Tried: both image tags (v2.2.3 and latest), switching regions
(us-west2 → us-east4), multiple redeploys. Same "failed to create deployment"
every time. Database service (evolution-db) is Online and healthy. Railway's
own agent diagnosed it as "Infrastructure Error".
This is a billable/paid service. I've exhausted everything on the dashboard side.
Please investigate the platform-side scheduling/container creation issue. Thanks!
Pinned Solution
a month ago
The image moved from atendai/evolution-api to evoapicloud/evolution-api.
Just change your source image to evoapicloud/evolution-api:v2.2.3 and you're set.
2 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
Since the container never gets created, start by ruling out the image itself.
Run the same image locally:
docker run --rm atendai/evolution-api:v2.2.3
If it starts successfully, the image is likely fine.
Next, deploy a minimal image such as nginx:alpine as a separate service in the same project. If that deploys successfully while atendai/evolution-api consistently fails during container creation, you've narrowed the problem down to the image rather than the project.
Also verify that the image is built for linux/amd64. If it's only available for a different architecture, Railway won't be able to create the container.
Could you also share the full deployment logs? "Failed to create deployment" is fairly generic, so the logs may contain the specific reason the container couldn't be created.
a month ago
The image moved from atendai/evolution-api to evoapicloud/evolution-api.
Just change your source image to evoapicloud/evolution-api:v2.2.3 and you're set.
Status changed to Solved medim • about 1 month ago