GPG error debian bookworm InRelease
corneliusio
PROOP

21 days ago

We keep getting the following error when trying to deploy changes to one of our services. It's not related to any code changes, and the diagnostic simply recommends trying to redeploy again each time. We've tried this a few times over the last few hours, but run into this same error each time.

I wasn't able to find any other threads that were specific to the GPG error, though it does seem like there are some ongoing issues with the Debian apt repository connection. Presumably this all ties back to the ongoing issues, but seems to be a somewhat novel presentation.


install apt packages: ca-certificates git unzip zip

Get:1 http://deb.debian.org/debian bookworm InRelease [151 kB]

Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]

Get:3 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]

Err:1 http://deb.debian.org/debian bookworm InRelease

  At least one invalid signature was encountered.

Err:2 http://deb.debian.org/debian bookworm-updates InRelease

  At least one invalid signature was encountered.

Err:3 http://deb.debian.org/debian-security bookworm-security InRelease

  At least one invalid signature was encountered.

Reading package lists...

W: GPG error: http://deb.debian.org/debian bookworm InRelease: At least one invalid signature was encountered.

E: The repository 'http://deb.debian.org/debian bookworm InRelease' is not signed.

W: GPG error: http://deb.debian.org/debian bookworm-updates InRelease: At least one invalid signature was encountered.

E: The repository 'http://deb.debian.org/debian bookworm-updates InRelease' is not signed.

W: GPG error: http://deb.debian.org/debian-security bookworm-security InRelease: At least one invalid signature was encountered.

E: The repository 'http://deb.debian.org/debian-security bookworm-security InRelease' is not signed.

Build Failed: build daemon returned an error < failed to solve: process "sh -c apt-get update && apt-get install -y ca-certificates git unzip zip" did not complete successfully: exit code: 100 >
Solved

1 Replies

Status changed to Awaiting Railway Response Railway 21 days ago


corneliusio
PROOP

21 days ago

It looks like the root of this issue has been resolved at some point. We are now able to deploy this service again.


Status changed to Solved corneliusio 21 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...