Deploy failing — "We don't have permission to execute your start command" (no Dockerfile/bin changes
hwhelchel
PROOP

4 days ago

Deploys failing since ~20h ago. Two services (web + worker) from same repo, both broken.

Worker error (Deploy > Create container): "We don't have permission to execute your start command."
Web error: Pre-deploy command failed (bin/rails db:migrate && bin/rails sitemap:generate).

Only change since last successful deploy: one Rake file (22 lines). No Dockerfile, bin/, Gemfile, or permission changes.

Verified via railway ssh on both running containers:

  • All bin/ scripts are 755, correct ownership (rails:rails)

  • Pre-deploy command runs fine (migrations up, sitemap generates)

  • Worker start command executes (only fails bind :80 because existing process holds it)

  • Build step succeeds, failure is at "Create container"

  • Redeployed multiple times, same result

    Setup: Rails, custom Dockerfiles (web + worker), multi-stage builds, chown -R rails:rails /rails, USER 1000:1000.

    Permission error is not reproducible inside the container. Feels platform-side — deploy pipeline running commands in a different context than the built image.

Closed

1 Replies

Status changed to Awaiting Railway Response medim 4 days ago


3 days ago

Please avoid opening duplicate threads.


Status changed to Awaiting User Response Railway 3 days ago


Status changed to Closed brody 3 days ago


Loading...