a month ago
Issue: Consistent build failures with corrupted/incomplete snapshot (59 kB). Nixpacks can't find source after unpacking. No code or config changes — previous builds succeeded.
Pinned Solution
a month ago
Probably because Nixpacks is deprecated or its using corrupted build cache
9 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
Salut
a month ago
Can you share your build logs? also Nixpacks is deprecated, I would recommend to use railpack or Dockerfile instead
mayori
Can you share your build logs? also Nixpacks is deprecated, I would recommend to use railpack or Dockerfile instead
a month ago
Does this help?
scheduling build on Metal builder "builder-arxrbc"
fetched snapshot sha256:6a4fea679080932610944a97beaafe76620345c4849e2779386474e4a1d01810 (59 kB bytes)
fetching snapshot
57.7 KB
unpacking archive
245.5 KB
using build driver nixpacks-v1.41.0
Error: Failed to read app source directory
Caused by:
No such file or directory (os error 2)nixpacks exited with an error
shaqdeezle
Does this help? scheduling build on Metal builder "builder-arxrbc" fetched snapshot sha256:6a4fea679080932610944a97beaafe76620345c4849e2779386474e4a1d01810 (59 kB bytes) fetching snapshot 57.7 KB unpacking archive 245.5 KB using build driver nixpacks-v1.41.0 Error: Failed to read app source directory Caused by: No such file or directory (os error 2) nixpacks exited with an error
a month ago
Attachments
a month ago
Try redeploy latest commit
Open your service > Open the command palette (Ctrl-K) > select Redeploy Latest Commit
If it didn't work, try create a new service with the same source
mayori
Try redeploy latest commit Open your service > Open the command palette (Ctrl-K) > select Redeploy Latest Commit If it didn't work, try create a new service with the same source
a month ago
So, my deployments are starting to work again. I'm unsure if the problem is resolved or if there's something specific, I can't deploy that causes it to error out.
shaqdeezle
So, my deployments are starting to work again. I'm unsure if the problem is resolved or if there's something specific, I can't deploy that causes it to error out.
a month ago
Probably because Nixpacks is deprecated or its using corrupted build cache
mayori
Probably because Nixpacks is deprecated or its using corrupted build cache
a month ago
Yeah, you're right. Once I switched to Dockerfile, everything started working again. Thank You for letting me know. I guess it switched automatically.
Status changed to Open 0x5b62656e5d • about 1 month ago
Status changed to Solved 0x5b62656e5d • about 1 month ago