10 days ago
Build failing repeatedly with: "Build Failed: build daemon returned an error < failed to solve: secret RAILWAY_GIT_REPO_OWNER not found >"
- Project: attractive-inspiration (91520e5b-8fe8-4e3d-97f1-7bb2130ddf86)
- Service: urban-coach-bot (e294f810-2940-4b9f-917c-0cb3292c300a)
- Environment: production
- Builder: RAILPACK v0.36.1, buildEnvironment V3, Metal builder
- Deploy method:
railway upfrom local directory (not linked to a GitHub repo) - Failure is consistent across 8+ deploy attempts over several hours (2026-08-11, ~17:00-19:20)
- Fails during the "install mise packages: python, uv" step, before pip install even runs
- One deploy DID succeed earlier today (deployment 99bda3be, ~17:10) with the exact same setup -- so it's not a config issue on our side, it's intermittent on Railway's build daemon
- Example failed deployment IDs: 9e3481c7-f9a0-47b9-b0c4-97402ea0e344, d0bd393a-39bb-4a02-8ed1-3076595be11f, 8ec4eb76-60b1-45bc-a722-01423e95359a, fdbeff7f-9a8a-40a8-a020-04988de69991, 14e1bbef-736c-44fd-8be0-1f6e3cd9939c, 44bd6c67-a97d-496b-a54d-bbbfed9f6926, 53fa0ed0-40ef-4915-a1ec-eb1cdeea7261, 7d59474b-6afb-49c9-a7d8-c480621d92a1
Question: is RAILWAY_GIT_REPO_OWNER expected to be populated automatically for services deployed via CLI railway up without a linked git repo? If so, is there a workaround to fix/set it, or is this a bug in the Metal/Railpack V3 build path?
1 Replies
10 days ago
Apologies for the trouble. We had an incident affecting Railpack builds, specifically isolated to users deploying via railway up, which has since been resolved. Your build failures fell within that window. Please try deploying again, and you can see the full timeline here: Railpack builds may be delayed
Status changed to Awaiting User Response Railway • 10 days ago
3 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 3 days ago