7 days ago
The error message is unfortunately quite vague and doesn't clearly indicate the actual problem.
If you've already verified that your configuration, syntax, and deployment settings are correct, the issue may be with the Docker image architecture.
In my case, the image was built for ARM64, while Railway expects an AMD64 (x86_64) image. Instead of showing a clear architecture mismatch, Railway returned this generic error.
Solution: Rebuild and push your Docker image for the AMD64/x86_64 platform. For example:
docker buildx build --platform linux/amd64 -t <your-image>:<tag> .After deploying the AMD64 image, the issue was resolved.
Attachments
1 Replies
7 days ago
That's correct, our infrastructure runs on AMD64/x86_64, so ARM64-only images will produce that misleading "could not be found" error. Building with --platform linux/amd64 is the fix. Thanks for sharing the solution!
Status changed to Awaiting User Response Railway • 7 days ago
Status changed to Solved Railway • 7 days ago