baseimage-gui-ubuntu images can't update

[loochao]

Thank you for your excellent work. Lately, I've been encountering issues when trying to build new Docker containers using baseimage-gui-ubuntu:22.04.

Initially, I'm able getting into the Docker environment.

$ docker run -it jlesage/baseimage-gui:ubuntu-22.04-v4 /bin/bash
root@808979963af2:/tmp#

Subsequently, the update fails, likely due to an issue specific to the Ubuntu Jammy Docker environment. However, I'm curious about the solution, especially since most of your other Docker images appear to have been updated successfully. Thank you!

root@808979963af2:/tmp# apt update
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' is not signed.

I attempted to make this key work, but it's complaining about gnupg, with no candidate available, leading to a dead end.

# apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 871920D1991BC93C
E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation

# apt install gnupg gnupg1 gnupg2 gnupgv

E: Package 'gnupg' has no installation candidate
E: Package 'gnupg1' has no installation candidate
E: Package 'gnupg2' has no installation candidate
E: Unable to locate package gnupgv

[jlesage]

It's working fine on my side:

$ docker pull jlesage/baseimage-gui:ubuntu-22.04-v4
$ docker run -it jlesage/baseimage-gui:ubuntu-22.04-v4 /bin/bash
root@a7bf1c4c1977:/tmp# apt update
Get:1 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
Get:2 http://security.ubuntu.com/ubuntu jammy-security InRelease [129 kB]
Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB]
Get:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [127 kB]
Get:5 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages [266 kB]
Get:6 http://archive.ubuntu.com/ubuntu jammy/restricted amd64 Packages [164 kB]
Get:7 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages [1792 kB]
Get:8 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages [17.5 MB]
Get:9 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [2674 kB]
Get:10 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages [1998 kB]
Get:11 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages [51.8 kB]
Get:12 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1410 kB]
Get:13 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [2263 kB]
Get:14 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 Packages [81.0 kB]
Get:15 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages [32.2 kB]
Get:16 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 Packages [44.7 kB]
Get:17 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages [2601 kB]
Get:18 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 Packages [1127 kB]
Fetched 32.6 MB in 3s (11.2 MB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
2 packages can be upgraded. Run 'apt list --upgradable' to see them.

Could it be related to a network issue on your side ?

[loochao]

Confirmed, it is now working on my machine as well. It appears that the key issue 'NO_PUBKEY 871920D1991BC93C,' which affected Ubuntu 22.04 (jammy), Ubuntu 24.04 (nobel), and Debian (bookworm), has been resolved upstream (e.g., I suspect that this key is now signed). At the time of my initial report, only Ubuntu 20.04 (focal) could be pulled and updated using apt. Please mark this issue as closed. Thank you for your help.

[jlesage]

Thanks for the update!