What base image are you using? (frappe/erpnext:v14, custom Dockerfile, etc.)

Your current Railway service configuration (any custom start command set?)

Your Dockerfile (if using one)

1: Set correct start command

Railway → Service Settings → Deploy → Custom Start Command:

bench start

bench start --web-port=$PORT

2: Debug what's actually in your container

ls -la /usr/local/bin/ && ls -la /home/frappe/frappe-bench/

3: Check for conflicting configs

Railway Variables tab → remove any CMD or ENTRYPOINT overrides

railway.toml → check for startCommand conflicts

Make sure nothing is setting /usr/local/bin/entrypoint.sh manually

If using custom Dockerfile

The official frappe/erpnext images use:

NTRYPOINT ["docker-entrypoint.sh"]

CMD ["bench", "start"]

NOT /usr/local/bin/entrypoint.sh

Why it keeps reverting:

Railway caches the deployment config from your first successful build. If that had the wrong path, it sticks. Solution: Delete service → Create fresh → Set correct command BEFORE first deploy