Hey ... so railway is detecting ur Dockerfile and completes the build. Right? If so, Does ur Dockerfile actually run your app? Have you set the correct `ENTERYPOINT` or `CMD` ? something like `CMD ["bin/rails", "server", "-b", "::", "-p", "3000"]`

in order to start the server you need a foreman command or rails server ``` ENTRYPOINT ["/rails/bin/docker-entrypoint"] CMD ["bundle", "exec", "foreman", "start", "-f", "Procfile"] ``` inside docker-entrypoint ``` #!/bin/bash -e echo "prepare db" # If running the rails server then create or migrate existing database if [ "$1" == "bundle" ] && [ "$2" == "exec" ] && [ "$3" == "foreman" ] && [ "$4" == "start" ]; then ./bin/rails db:prepare echo "prepared db" fi exec "${@}" ``` with rails server ``` ENTRYPOINT ["/rails/bin/docker-entrypoint"] CMD ["bin/rails", "server"] ``` ``` if [ "${@: -2:1}" == "bin/rails" ] && [ "${@: -1:1}" == "server" ]; then ./bin/rails db:prepare fi ``` make sure to adjust the path to the \`docker-entrypoint\`

Yeah same as above. docker-entrypoint has this: ```shellscript #!/bin/bash -e # Enable jemalloc for reduced memory usage and latency. if [ -z "${LD_PRELOAD+x}" ]; then LD_PRELOAD=$(find /usr/lib -name libjemalloc.so.2 -print -quit) export LD_PRELOAD fi # If running the rails server then create or migrate existing database if [ "${@: -2:1}" == "./bin/rails" ] && [ "${@: -1:1}" == "server" ]; then ./bin/rails db:prepare fi exec "${@}" ``` Again, all by default with Rails 8, I didn't change anything

I’ve seen that exact entrypoint logic before with new Rails apps. But I think the main issue is with the `CMD` using `./bin/thrust`, which might not behave the way Railway expects. Since Railway looks for a process listening on `$PORT`, and that might not be happening here, it shuts things down thinking the container failed. Try replacing the CMD entirely with this in your Dockerfile: \`\`\`dockerfile CMD \["bin/rails", "server", "-b", "0.0.0.0", "-p", "${PORT}"\] Or just override it in the Railway dashboard with: bin/rails db:prepare && bin/rails server -b 0.0.0.0 -p $PORT

I've overwritten it in the Railway dashboard exactly like that and that didn't work. Let me try changing the dockerfile when I'm back on my computer and see.

Hey! Here’s a few things that might help you fix the container shutdown issue: **What you’re doing right** * Dockerfile is detected * Environment variables are correctly set : RAILS\_ENV=production DATABASE\_URL=<your PostgreSQL URL> RAILS\_MASTER\_KEY=<your master key> * Deploy status shows as successful ⚠ **Likely issue** Your container is likely exiting because the Rails server process doesn’t stay alive — this is often due to incorrect binding address or port configuration. **Fix suggestion** 1. Use 0.0.0.0 instead of :: for binding. Railway expects an IPv4 address. bin/rails db:prepare && bin/rails server -b 0.0.0.0 -p $PORT 1. Make sure you’re using $PORT. Railway injects this variable — your app must bind to it. 2. Optional: Add a Procfile if you’re not already using one: web: bin/rails server -b 0.0.0.0 -p $PORT 1. If logs only show “Starting/Stopping Container”, try adding logging inside your Dockerfile or entrypoint to verify the server process is starting and staying alive.

Hey! I dug into the full thread and I believe the issue is related to a mismatch between how Railway expects containers to behave and how `bin/thrust` is handling the Rails server. \--- # 🔍 Root cause: Your Dockerfile defines: \`\`\`dockerfile CMD \["./bin/thrust", "./bin/rails", "server"\] But `thrust` likely forks or delegates the Rails process in a way that **Railway can’t track** — so Railway shuts down the container assuming it crashed, since it sees no active foreground process. Verified fix (keeping Docker): 1. **Replace the CMD** in the Dockerfile with: CMD \["bin/rails", "server", "-b", "0.0.0.0", "-p", "${PORT}"\] 2. Ensure you **don’t override** this in the Railway dashboard — Railway will use the CMD from your Dockerfile if a valid ENTRYPOINT exists. 3. Optional: add `ENTRYPOINT ["./docker-entrypoint.sh"]` that logs before calling `exec "$@"`. 4. Confirm the app listens on `$PORT` — Railway requires this to detect success. If you still want to use `thrust`, you’d have to ensure it: * **runs Rails as PID 1** * **doesn't fork in background** * or wrap it in `exec` to promote the child to PID 1. But best practice: remove `thrust`, use `rails server` directly in Docker. Let me know if you want a working Dockerfile template! Happy to help 🙂 \---