Every railway up deploy has failed since 2026-07-31. The upload succeeds, but the build

dies immediately at "[internal] load build context" with this error:

failed to solve: Internal: rpc error: code = Internal desc = rpc error: code = Internal

desc = header key "exclude-patterns" contains value with non-printable ASCII characters

Details

---

Project: gallant-fascination (984ad883-85a4-4130-b5a0-1fdbc8a39f97)

Environment: production

Service: Aura

Builder: builder-vefplu (every attempt was scheduled on this same builder)

Deploy type: railway up (CLI upload)

Builder type: DOCKERFILE

Failed deployments

---

ab422e75-c758-41f7-b1dd-3528cd8d1c9d

903c21a6-36e1-45eb-8430-1f79e6cdb0e4

a0a621c4-3412-43ef-971f-288d48bac2a2

578b41b8-c95f-4104-820a-ed50e90e8e49

666e4e8e-da92-4f4c-b6b6-a753b0ff49d1

Last successful build: a57bd915-7090-4f62-bc14-f3ff02537ac1 (2026-07-26T11:13:31Z)

Nothing in our build configuration changed between that build and the first failure.

What I have already ruled out

---

1. .dockerignore contents — reduced it to two pure-ASCII lines with LF endings.

   Still fails with the identical error, so the header value cannot be coming

   from our ignore file contents.

2. .gitignore contents — all comments converted to ASCII, working copy normalised

   from CRLF to LF. No change.

3. CLI version — reproduced identically on 5.30.1 and on 5.27.2 (the version that

   deployed this same project successfully on 2026-07-22). Not a CLI regression.

4. Service configuration — watchPatterns is empty, rootDirectory is null.

5. Local BuildKit — docker build against the exact same directory works fine:

   the context transfers and COPY succeeds. Only Railway's builder rejects it.

6. No incidents listed on status.railway.com.

Question

---

Could someone check what builder-vefplu is putting into the exclude-patterns header

for this service, or move the service onto a different builder? I am happy to run

any diagnostic command you need.