GitHub user n-oden closed a discussion: apt repository keys no longer 
functioning

### Apache Airflow version

2.10.4

### If "Other Airflow 2 version" selected, which one?

_No response_

### What happened?

The documentation at 
https://airflow.apache.org/docs/docker-stack/build.html#build-build-image 
suggests that it should be possible to run `apt-get update` in the context of 
the upstream `apache/airflow:2.10.4` docker image.  However, this no longer 
appears to be the case:

```
$ docker run -it --entrypoint=/bin/bash --user root apache/airflow:2.10.4
root@fffa6fd0bf12:/opt/airflow# apt-get update
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 https://download.docker.com/linux/debian bookworm InRelease [43.3 kB]
Get:4 https://packages.microsoft.com/debian/12/prod bookworm InRelease [3618 B]
Get:5 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.
Get:6 https://archive.mariadb.org/mariadb-10.11/repo/debian bookworm InRelease 
[4625 B]
Err:2 http://deb.debian.org/debian bookworm-updates InRelease
  At least one invalid signature was encountered.
Get:7 https://apt.postgresql.org/pub/repos/apt bookworm-pgdg InRelease [129 kB]
Err:3 https://download.docker.com/linux/debian bookworm InRelease
  At least one invalid signature was encountered.
Err:4 https://packages.microsoft.com/debian/12/prod bookworm InRelease
  At least one invalid signature was encountered.
Err:5 http://deb.debian.org/debian-security bookworm-security InRelease
  At least one invalid signature was encountered.
Err:6 https://archive.mariadb.org/mariadb-10.11/repo/debian bookworm InRelease
  At least one invalid signature was encountered.
Err:7 https://apt.postgresql.org/pub/repos/apt bookworm-pgdg InRelease
  At least one invalid signature was encountered.
Reading package lists... Done
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: https://download.docker.com/linux/debian bookworm InRelease: At 
least one invalid signature was encountered.
E: The repository 'https://download.docker.com/linux/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: https://packages.microsoft.com/debian/12/prod bookworm InRelease: 
At least one invalid signature was encountered.
E: The repository 'https://packages.microsoft.com/debian/12/prod 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-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.
W: GPG error: https://archive.mariadb.org/mariadb-10.11/repo/debian bookworm 
InRelease: At least one invalid signature was encountered.
E: The repository 'https://archive.mariadb.org/mariadb-10.11/repo/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: https://apt.postgresql.org/pub/repos/apt bookworm-pgdg InRelease: 
At least one invalid signature was encountered.
E: The repository 'https://apt.postgresql.org/pub/repos/apt bookworm-pgdg 
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.
```

### What you think should happen instead?

`apt-get update` and/or `apt update` should return successfully, having 
downloaded the apt server lists from all sources.

### How to reproduce

1. `docker run -it --entrypoint=/bin/bash --user root apache/airflow:2.10.4 -c 
'apt-get update'`

That's really it: you'll see the "invalid signature" errors and a return code 
of 100.

### Operating System

PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" 
VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian 
HOME_URL="https://www.debian.org/"; SUPPORT_URL="https://www.debian.org/support"; 
BUG_REPORT_URL="https://bugs.debian.org/";

### Versions of Apache Airflow Providers

n/a

### Deployment

Other Docker-based deployment

### Deployment details

n/a -- this is an issue with the docker image itself

### Anything else?

_No response_

### Are you willing to submit PR?

- [x] Yes I am willing to submit a PR!

### Code of Conduct

- [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)


GitHub link: https://github.com/apache/airflow/discussions/45648

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to