23 days ago
Project dps-evolution-api (production), service evolution-api (Docker image atendai/evolution-api). Hobby plan, card on file, usage ~$3.23/$5 included, compute hard limit $150 (not reached). EVERY deployment fails instantly (~00:01) at "Deploy > Create container: Failed to create deployment"; post-deploy never starts; the auto-Diagnosis mentions "out of memory / resource allocation". Tried, all fail the same: redeploy v1.8.7 and v2.2.3; removed both volumes; enabled Teardown (overlapSeconds 0); changed region us-west2 -> us-east4; and created a brand-new service from scratch (also fails at Create container). Existing containers keep running fine (Postgres is up). Only NEW container creation fails, in every region and even on a fresh service. Please investigate and lift whatever is blocking new container creation on this account — our production WhatsApp API is offline. Thank you.
2 Replies
23 days ago
Every deployment on this account is failing because the Docker image docker.io/atendai/evolution-api:v2.2.3 cannot be pulled - the error is an image pull failure, not a resource or container-creation block. There are no restrictions or limit issues on the account. The image tag may have been removed or renamed on Docker Hub, or Docker Hub may be rate-limiting pulls. You can verify the tag still exists at the image's Docker Hub page, and if it has moved, update the image reference in your service's source settings to the current tag.
Status changed to Awaiting User Response Railway • 23 days ago
23 days ago
The image is moved to evoapicloud/evolution-api, change your image to evoapicloud/evolution-api:v2.2.3
Status changed to Awaiting Railway Response Railway • 23 days ago
Status changed to Awaiting User Response Railway • 23 days ago
16 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 • 16 days ago