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

Created on 18 Apr 2021  ยท  4Comments  ยท  Source: docker-library/python

I have the following Dockerfile:

FROM python:3.8-buster
RUN apt-get update -q

When I run docker build . I get:

[+] Building 1.2s (5/5) FINISHED                                                           
 => [internal] load build definition from Dockerfile.cpu                              0.0s
 => => transferring dockerfile: 40B                                                   0.0s
 => [internal] load .dockerignore                                                     0.0s
 => => transferring context: 34B                                                      0.0s
 => [internal] load metadata for docker.io/library/python:3.8-buster                  0.4s
 => CACHED [1/2] FROM docker.io/library/python:3.8-buster@sha256:d8c335648469f670530  0.0s
 => ERROR [2/2] RUN apt-get update -q                                                 0.7s
------                                                                                     
 > [2/2] RUN apt-get update -q:                                                            
#5 0.378 Get:1 http://deb.debian.org/debian buster InRelease [121 kB]                      
#5 0.378 Get:2 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]                                                                                          
#5 0.434 Get:3 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]             
#5 0.491 Err:2 http://security.debian.org/debian-security buster/updates InRelease
#5 0.491   At least one invalid signature was encountered.
#5 0.557 Err:1 http://deb.debian.org/debian buster InRelease
#5 0.557   At least one invalid signature was encountered.
#5 0.605 Err:3 http://deb.debian.org/debian buster-updates InRelease
#5 0.605   At least one invalid signature was encountered.
#5 0.610 Reading package lists...
#5 0.621 W: GPG error: http://security.debian.org/debian-security buster/updates InRelease: At least one invalid signature was encountered.
#5 0.621 E: The repository 'http://security.debian.org/debian-security buster/updates InRelease' is not signed.
#5 0.621 W: GPG error: http://deb.debian.org/debian buster InRelease: At least one invalid signature was encountered.
#5 0.621 E: The repository 'http://deb.debian.org/debian buster InRelease' is not signed.
#5 0.621 W: GPG error: http://deb.debian.org/debian buster-updates InRelease: At least one invalid signature was encountered.
#5 0.621 E: The repository 'http://deb.debian.org/debian buster-updates InRelease' is not signed.
------
executor failed running [/bin/sh -c apt-get update -q]: exit code: 100

Surely there is something pretty basic I am missing here.

โฏ docker --version
Docker version 20.10.5, build 55c4c88

Most helpful comment

I'm seeing this consistently now. Seems likely to be a debian mirror issue, as I can reproduce it with a simple docker run debian:buster apt-get update

Sorry, not related. The issue was running out of disk space in the docker for mac VM. (I thought I'd checked this already)

All 4 comments

I'm not able to reproduce, so either it was a temporary issue with the mirror or it could be something related to the host's environment https://github.com/docker-library/php/issues/898

$ docker build -t python:test - <<EOF
> FROM python:3.8-buster
> RUN apt-get update -q
> EOF
Sending build context to Docker daemon  2.048kB
Step 1/2 : FROM python:3.8-buster
3.8-buster: Pulling from library/python
bd8f6a7501cc: Pull complete 
44718e6d535d: Pull complete 
efe9738af0cb: Pull complete 
f37aabde37b8: Pull complete 
3923d444ed05: Pull complete 
1ecef690e281: Pull complete 
48673bbfd34d: Pull complete 
b761c288f4b0: Pull complete 
57ed4d1661b5: Pull complete 
Digest: sha256:d8c335648469f6705307956df04395678f3b0a859eaa68806d773489c77cc273
Status: Downloaded newer image for python:3.8-buster
 ---> 02583ab5c95e
Step 2/2 : RUN apt-get update -q
 ---> Running in cd716a687e08
Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Get:2 http://deb.debian.org/debian buster InRelease [121 kB]
Get:3 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
Get:4 http://security.debian.org/debian-security buster/updates/main amd64 Packages [272 kB]
Get:5 http://deb.debian.org/debian buster/main amd64 Packages [7907 kB]
Get:6 http://deb.debian.org/debian buster-updates/main amd64 Packages [9504 B]
Fetched 8427 kB in 2s (4449 kB/s)
Reading package lists...
Removing intermediate container cd716a687e08
 ---> 84884f6ae5bd
Successfully built 84884f6ae5bd
Successfully tagged python:test

I'm seeing this consistently now. Seems likely to be a debian mirror issue, as I can reproduce it with a simple docker run debian:buster apt-get update

Sorry, not related. The issue was running out of disk space in the docker for mac VM. (I thought I'd checked this already)

Yep as @grncdr noticed, seems really similar to https://github.com/debuerreotype/docker-debian-artifacts/issues/107 (which was also running out of disk space in the VM). :smile:

Yes docker system prune fixed it. Thanks!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

harsha-y picture harsha-y  ยท  5Comments

JulienPalard picture JulienPalard  ยท  3Comments

DiedeGu picture DiedeGu  ยท  4Comments

yashbhutwala picture yashbhutwala  ยท  4Comments

NoirPi picture NoirPi  ยท  4Comments