No build logs. This is all that shows. All of the builds seem to immediately fail ![image.png](https://station-server.railway.com/attachments/att_01kxfcdza5en9s5xq9kcxs4vx9)

Builds failing - Railway Central Station

Builds failing

devcshort

PROOP

a month ago

No build logs. This is all that shows. All of the builds seem to immediately fail

Attachments

image.png

Solved

5 Replies

Status changed to Awaiting Railway Response Railway • about 1 month ago

noahd

EMPLOYEE

a month ago

Hey! Can you try hitting cmd + k and "deploy latest commit"? I don't see any erroneous logs on our end. Would love to monitor a new deploy and see any live failures.

Status changed to Awaiting User Response Railway • about 1 month ago

noahd

Hey! Can you try hitting `cmd + k` and "deploy latest commit"? I don't see any erroneous logs on our end. Would love to monitor a new deploy and see any live failures.

devcshort

PROOP

a month ago

Hey, just ran that. It seems that the build is failing before we get any sort of log output on our side.

Attachments

image.png

Status changed to Awaiting Railway Response Railway • about 1 month ago

devcshort

Hey, just ran that. It seems that the build is failing before we get any sort of log output on our side. ![image.png](https://station-server.railway.com/attachments/att_01kxhfzzknen8axdeefcytqers)

devcshort

PROOP

a month ago

Screenshot of logs from that deploy

Attachments

image.png

sam-a

EMPLOYEE

a month ago

Found it. Your builds are failing in the Dockerfile's apt step: it pins curl=7.88.1-10+deb12u14, and Debian recently replaced that version, so apt can't find it anymore and exits with code 100. That's also why the last good build was July 1 and everything since July 13 fails instantly.

Updating the pin to the current curl version, or installing curl without a version pin, will fix it.

Railway Team

Status changed to Awaiting User Response Railway • about 1 month ago

sam-a

Found it. Your builds are failing in the Dockerfile's apt step: it pins `curl=7.88.1-10+deb12u14`, and Debian recently replaced that version, so apt can't find it anymore and exits with code 100. That's also why the last good build was July 1 and everything since July 13 fails instantly. Updating the pin to the current curl version, or installing `curl` without a version pin, will fix it. Railway Team

devcshort

PROOP

a month ago

😕 shoot, we should have caught that. Thank you for your help! We'll get that updated and retested

Status changed to Awaiting Railway Response Railway • about 1 month ago

Status changed to Solved Railway • about 1 month ago

Welcome!