Diagnosis : All recent deployments are failing due to a persistent infrastructure issue with the build daemon. The connection to the builder drops before any Dockerfile instructions can execute, producing an EOF error. Retrying may not help since multiple consecutive deployments have failed the same way. Reach out to Railway support to investigate.

shouuld be fixed

internal

load build definition from Dockerfile

0ms

internal

load .dockerignore

0ms

Build Failed: build daemon returned an error < failed to receive status: rpc error: code = Unavailable desc = error reading from server: EOF >

It has not yet been resolved 😑

Solution ? 48hs with this problem

For a workaround, disable the metal builder in the service settings

See if that works

Its is already disabled and its still the same

Diagnosis : Every deployment for this service has been failing since April 23 due to a persistent build infrastructure issue. The build daemon drops its connection with an EOF error immediately after parsing the Dockerfile, before any build steps can execute. This has occurred across 10+ deployments on multiple different builder instances and is not caused by any code or configuration change.

can you try to rebuild?

I see successful builds on the same builder, surprising you got this error

Yes, and I get the same error I posted previously: "is not caused by any code or configuration change"

Nothing? Deam 72hs this problem

We need more time to understand the problem. The only solution right now is to disable Metal builders here:

It was the first thing I deactivated and nothing changed.

from what I see, right now it is enabled

I just checked what you said and you're right, why is it activating itself? I've attached a screenshot showing that I deactivated it again.