All builds FAIL on Metal builder "builder-ryvidd" — snapshot-target-unpack/main missing
walmirmariano
HOBBYOP

4 days ago

Hi Railway team,

All deployments for my service kairos-web (project efa8ffdf-96bf-4e76-a5a9-3541b675b810, service

06ab87ef-dd84-44d4-8df2-73b6bd6e849c) have FAILED since 2026-07-01 19:05:54 UTC-3 — that's 6 consecutive

failed deploys over ~24 hours.

The last successful deploy was 76aad374 on 2026-07-01 19:01:54 UTC-3. Production is still Online serving

traffic from that container.

Error pattern (consistent across all 6 failures):

[INFO] fetching snapshot

[INFO] unpacking archive                                                                                   

using build driver railpack-v0.30.0   (or nixpacks-v1.41.0)                                                

Error: Failed to read app source directory                                                                 

Caused by: No such file or directory (os error 2)                                                          

railpack/nixpacks exited with an error                                                                     

scheduling build on Metal builder "builder-ryvidd"                                                         

Root cause appears to be Metal builder "builder-ryvidd" — the snapshot-target-unpack/main/ directory is never

created on the builder, regardless of build driver (railpack or nixpacks). Both fail reading from the same

missing path.

Things I've already tried:

- Multiple git push deploys (5 attempts) — same error
- railway up (direct upload, bypasses git snapshot) — same error                                           
- Switched builder from railpack to nixpacks via railway.toml [build] builder = "nixpacks" — same root     

error, confirming it's the builder not the driver

- Verified Dockerfile is valid and builds locally                                                          
- Verified production container is healthy (deploy 76aad374 from 07-01 still serving)                      

This is blocking all new deploys. Can you either:

1. Remove/repair builder-ryvidd from the pool, or                                                          
2. Re-route my service to a different Metal builder, or                                                    
3. Disable Metal builder for my service so it uses the legacy non-Metal builder?                           

Recent failed deployment IDs for reference:

- 1c3bb133-24a9-411f-9cfb-796d468782da (most recent, nixpacks bypass attempt)                              
- 1469fde1-f87c-47e6-8788-b392479e76fa (railway up direct upload)                                          
- 2dd6ba45-e707-4d94-a52b-aa69d9d03a46                                                                     
- 6d061d20-fa3f-4d34-acf0-8452366782ac                                                                     
- 1be4eb10-c354-40c6-ac4f-6f5e094ad603                                                                     
- 33172070-20d8-4c3b-9aaa-cf9ee505b176 (first failure, 07-01 19:05:54)                                     

Thanks,

Walmir Mariano

Solved

0 Replies

Status changed to Awaiting Railway Response Railway 4 days ago


Status changed to Solved walmirmariano 4 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...