API service build failing after aborted stuck deploy (Failed to read app source directory)
variousfoot
HOBBYOP

2 months ago

I need help with what looks like a builder/cache issue on one service.

Error:

  • Error: Failed to read app source directory
  • Caused by: No such file or directory (os error 2)
  • nixpacks exited with an error

What happened:

  1. A deployment got stuck at “Creating containers”.
  2. I aborted/removed that stuck deployment.
  3. Since then, every new deployment for this API service only fails at image build with the same error.

It would seem this is an internal issue and nothing is flagged on railway status page.

Solved

1 Replies

variousfoot
HOBBYOP

2 months ago

UPDATE: had to redeploy a new service inside the existing project to fix the stuck version


Status changed to Awaiting Railway Response Railway about 2 months ago


Status changed to Solved brody about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...