Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid Signature while trying to update debian packages #1094

Open
jdlarrubia opened this issue Nov 8, 2024 · 1 comment
Open

Invalid Signature while trying to update debian packages #1094

jdlarrubia opened this issue Nov 8, 2024 · 1 comment

Comments

@jdlarrubia
Copy link

jdlarrubia commented Nov 8, 2024

Hi!

I am running into an issue with all mysql 8 debian images. I cannot do a simple apt-get update because it refers to an invalid signature in mysql package.

My simple dockerfile:

FROM mysql:8.0.40-debian
RUN apt-get update && apt-get -y install python3-pip

The output:

Get:1 http://repo.mysql.com/apt/debian bookworm InRelease [22.7 kB]
Get:2 http://deb.debian.org/debian bookworm InRelease [151 kB]
Get:3 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
Err:1 http://repo.mysql.com/apt/debian bookworm InRelease
  At least one invalid signature was encountered.
Get:4 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Err:2 http://deb.debian.org/debian bookworm InRelease
  At least one invalid signature was encountered.
Err:3 http://deb.debian.org/debian bookworm-updates InRelease
  At least one invalid signature was encountered.
Err:4 http://deb.debian.org/debian-security bookworm-security InRelease
  At least one invalid signature was encountered.
Reading package lists... Done
W: GPG error: http://repo.mysql.com/apt/debian bookworm InRelease: At least one invalid signature was encountered.
E: The repository 'http://repo.mysql.com/apt/debian bookworm InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
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.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
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.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
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.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details

I've been looking into the issues, but the last one referring to gpg keys is from 2022. I cannot think that I am the only one trying to update my packages.

Am I doing something wrong? Is there any solution to this?

@tianon
Copy link
Member

tianon commented Nov 8, 2024

This is probably either docker-library/official-images#16829 or a misbehaving (MITM) proxy, which is common in corporate environments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants