Comment 7 for bug 1956039

Revision history for this message
EchoPouet (arnaudmoura) wrote (last edit ):

I have a Dockerfile to test this issue. In the Docker image have this issue after install git package.

Dockerfile use with Docker v20.10.20 :
FROM ubuntu:22.04

RUN apt-get update && apt-get upgrade --yes && apt-get install --yes \
    curl

RUN apt-get install --yes \
    git

I created container from this image and I have this error:
/# apt install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@9f96e185ff6a:/# apt update
Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
Get:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [114 kB]
Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease
  The following signatures were invalid: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018) <email address hidden>
Get:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [99.8 kB]
Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
Fetched 484 kB in 0s (1135 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.ubuntu.com/ubuntu jammy InRelease: The following signatures were invalid: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018) <email address hidden>
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease The following signatures were invalid: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018) <email address hidden>
W: Some index files failed to download. They have been ignored, or old ones used instead.