8 months ago
Hello,
I have started a project based on https://github.com/rpuls/medusajs-2.0-for-railway-boilerplate (https://railway.app/template/gkU-27) then I have cloned the medusajs-2.0-for-railway-boilerplate repo, changed remote and pushed to my own repo. Afterwards I have changed the repo in the settings in railway to my (fork alike) repo, linked to railway via railway cli and executed "railway up".
Now the deployment in railway (for the backend service) started but is stuck at "creating containers" - after > 10 min the deployment is marked as failed.
The build logs ends like:
=== Successfully Built! ===
docker run -it europe-west4.registry.rlwy.net/55084aba-8a5b-49eb-9078-eb69605831f9:81727692-d08e-40ef-b05d-f1d5222ef5e6
Build time: 80.92 seconds
ⓘ Deployment information is only viewable by project members and Railway employees.
6 Replies
8 months ago
I have the same issue and it's a very serious problem. Medusa 2.0 is failing to create container or finish the deployment:
Attachments
8 months ago
I've tried to run it with node 22 too, but it didn't worked
8 months ago
I just wonder how the railway-boilerplate did work at first place. My first deployment was working. I changed nothing else then the repo endpoint and the function location (to amsterdam).
8 months ago
I tried with node 20 the result is the same... Never worked. Locally works like a charm with any node >= 20
8 months ago
I saw that yarn.lock was added to gitignore and nixpack was trying to install and build the project with npm . I've added yarn.lock to version control. Now it started to install and build with yarn but failed again with the same issue...
8 months ago
I have set up the same project (from boilerplate) again as a new project and did this time not change the function location. It is working now. Although I need to deploy via "railway up" as the git hook seems not to be working (I can push without any effect in the new project).