package updates with apt not working

[andreasnef]

Hi

These past days, I experienced a problem when trying to update to the latest version of 8.5-jre8:

$ docker build --progress plain -f Dockerfile.test .
#1 [internal] load build definition from Dockerfile.test
#1 sha256:7fbe8bdf149b13038d4f03d39c0999510ec00620583712cf2219d88850d41bb0
#1 transferring dockerfile: 41B done
#1 DONE 0.0s

#2 [internal] load .dockerignore
#2 sha256:9c23d0a13206141673d688c0b8e2273570db61b9f482cd22b8064bda271e0c19
#2 transferring context: 34B done
#2 DONE 0.0s

#3 [internal] load metadata for docker.io/arm64v8/tomcat:8.5-jre8
#3 sha256:94cb84f3a057703e23f74b4f458dd847590d9e5826dc1bf6e1bb94f98cfb47e8
#3 DONE 1.1s

#4 [1/2] FROM docker.io/arm64v8/tomcat:8.5-jre8@sha256:6827d06d478c67039fa1bbbf68f361a0697af20bfed7e6254175c95365e0c236
#4 sha256:ca8bd80973469b059c2afb55e051cb4c536831e7b099d228098fb9a25866215c
#4 CACHED

#5 [2/2] RUN apt-get update
#5 sha256:1e6d60ee70941d837bd650a049c453616ae4a109ee02458ee946684ef7bc4372
#5 0.334 Get:1 http://ports.ubuntu.com/ubuntu-ports jammy InRelease [270 kB]
#5 1.021 Get:2 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease [114 kB]
#5 1.056 Err:1 http://ports.ubuntu.com/ubuntu-ports jammy InRelease
#5 1.056   At least one invalid signature was encountered.
#5 1.177 Err:2 http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease
#5 1.177   At least one invalid signature was encountered.
#5 1.217 Get:3 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease [99.8 kB]
#5 1.400 Err:3 http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease
#5 1.400   At least one invalid signature was encountered.
#5 1.402 Get:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease [110 kB]
#5 1.541 Err:4 http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease
#5 1.541   At least one invalid signature was encountered.
#5 1.545 Reading package lists...
#5 1.554 W: GPG error: http://ports.ubuntu.com/ubuntu-ports jammy InRelease: At least one invalid signature was encountered.
#5 1.554 E: The repository 'http://ports.ubuntu.com/ubuntu-ports jammy InRelease' is not signed.
#5 1.554 W: GPG error: http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease: At least one invalid signature was encountered.
#5 1.554 E: The repository 'http://ports.ubuntu.com/ubuntu-ports jammy-updates InRelease' is not signed.
#5 1.554 W: GPG error: http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease: At least one invalid signature was encountered.
#5 1.554 E: The repository 'http://ports.ubuntu.com/ubuntu-ports jammy-backports InRelease' is not signed.
#5 1.554 W: GPG error: http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease: At least one invalid signature was encountered.
#5 1.554 E: The repository 'http://ports.ubuntu.com/ubuntu-ports jammy-security InRelease' is not signed.
#5 ERROR: executor failed running [/bin/sh -c apt-get update]: exit code: 100
------
 > [2/2] RUN apt-get update:
------
executor failed running [/bin/sh -c apt-get update]: exit code: 100
$

The Dockerfile.test is really just the following:

FROM arm64v8/tomcat:8.5-jre8

RUN apt-get update

EXPOSE 8080

I've seen #270, and navigated to tianon/docker-brew-ubuntu-core#248, but not sure what this actually means for the above – the official image has been updated just two days ago.

Using docker 4.13.0 (89412) and engine 20.10.20.

[tianon]

This typically means that either your Docker host filesystem (inside the VM, if you're on Docker Desktop) is full or that you need a newer version of libseccomp.

[andreasnef]

Hi

I'm on macOS, and went through the different suggestions from docker/for-mac#6030, and docker system prune actually resolved the issue.