build failed with error of 502
neolee98
PROOP

a month ago

Build Failed: build daemon returned an error < failed to solve: failed to resolve source metadata for ghcr.io/railwayapp/railpack-frontend:v0.27.0: failed to authorize: failed to fetch oauth token: unexpected status from GET request to https://ghcr.io/token?scope=repository%3Arailwayapp%2Frailpack-frontend%3Apull&service=ghcr.io: 502 Bad Gateway: 


  
... (54634 bytes truncated) >

10 Replies

Try redeploying the service.


neolee98
PROOP

a month ago

now it works, wired that 2 services failed with this error twice


neolee98
PROOP

a month ago

btw do we have a wait for service in railway?


Could've been a one off thing. I was able to pull that image just fine locally.


What do you mean?


neolee98
PROOP

a month ago

so when auto redeploy from github push, serviceA wait for serviceB before rebuild


neolee98
PROOP

a month ago

cause serviceA have something need from B during build


I'd suggest building a custom CI/CD pipeline that waits for service B to finish deploying, as well as disabling automatic deployments on service A.


neolee98
PROOP

a month ago

ah like a CI/CD that use railway api to trigger build?


Yes, via Github Actions.

You can also use Railway's webhooks to call Railway functions to trigger a deployment.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...