Adding urgency/context: this blocks production rollout today. We retried API twice and Web once; both still fail before bun install while resolving railpack-frontend:v0.30.0. Current production is online, but we cannot ship the release.

Update: we unblocked production by temporarily switching both API and Web from Railpack to Nixpacks.

The original failure still looks like a Railpack/builder issue, because builds failed before app install/build while resolving:

ghcr.io/railwayapp/railpack-frontend:v0.30.0

with:

frontend grpc server closed unexpectedly

After switching to Nixpacks, the deploy reached the build plan. We then had to pin Node to >=22.15.0 because Nixpacks selected Node 18, which is EOL/removed from Nix. After that, deployment succeeded.

So production is unblocked, but please still investigate the Railpack failure. We would like to know whether Railpack v0.30.0 is currently safe to use again, or whether we should stay on Nixpacks for now.

Hey!

Not at all ideal, could you link one of the failing railpack deploys? Or even switch back to railpack and see if it was something transient? Would love to pinpoint exactly what it is

Here is one failing Railpack deploy:

https://railway.com/project/822c34b7-cd29-4ab9-8a4e-6a8e6b48868f/service/892922a4-23d0-42b8-a4b9-8d07f70e7ac5?environmentId=4225f711-f7f5-494b-aae2-2e71e71a0115&id=75a2d901-ae70-468d-8015-a447e2962ada

It failed during Railpack image build with:

Build Failed: build daemon returned an error < failed to solve: frontend grpc server closed unexpectedly >

I’d prefer not to switch back to Railpack until you can confirm it looks stable or that the issue was transient.

I attached a ticket so we can track this issue best. If I have any updates will forward them your way

Heard back from our platform team, looks like this was a transient builder issue. You shouldnt run into it again.

Yes it works now.