Hi! Can you provide some logs? In what step is it stuck on?

It seems to fail to call the health endpoint. It was fixed by removing all the regions, only leaving one.

I also have Metal build env. enabled. I saw it might be the reason why.

Hey there!

I took a look at the linked resource -- it looks like it took your health check 1 second to succeed on the linked resource.

I'm not seeing any issues with the current build, but just in case I can offer some general deployment speed advise:

You can improve your Build and Deployment times a few main ways:

1. Reduce your container size. The resulting container from your build needs to be packaged up, uploaded to Railway's registry, and then downloaded on your deploying workload. Any space you can save can decrease the times for each of these processes. You may want to look at your package manager and see what dependencies you can remove, or look at your Dockerfile and see if you can use a smaller, more production-ready base image.

2. Reduce your Resource Limits. If you're using replicas, Railway's orchestrator has to find space for the number of replicas * the Resource Limits you have set on the Settings tab. Lowering these limits to a more realistic size for your workload can decrease the time it takes for the orchestrator to schedule your workload.