Problems with current Debian 12.x Containers - Possibly Defective on Docker
(Host is running RHEL9 with FIPS enabled. Pulling and running rootless containers with podman)
The Debian 12.5 image (registry1.dso.mil/ironbank/opensource/debian/debian:12.5) seems to be broken and needs to be fixed. Specifically, running "apt update" or "apt upgrade" in the console fails, with "fatal error in libgcrypt, file ../../src/misc.c, line 92, function _gcry_fatal_error: requested algo not in md context. Fatal error: requested algo not in md context Aborted (core dumped)"
The Debian:12.4 image (registry1.dso.mil/ironbank/opensource/debian/debian 12.4) is good, running "cat /etc/debian_version" returns "12.5". Looking at the History in podman indicates apt update and apt upgrade were run as part of the build, so it's understandable that it would say 12.5.
Harbor only has one image tagged with "12.4" and one with "12.5", so it should be easy to pull and check against other environments.
I downloaded several debian:12.5-based images: registry1.dso.mil/ironbank/opensource/debian/debian:12.5 registry1.dso.mil/ironbank/opensource/debian/debian12/openjdk@sha256:9923f91fa7e1990989a9ff5be1a44c3e2ff318605185fa8e6519e3c5b9282b46 registry1.dso.mil/ironbank/jdk/debian/debian12/jdk21-slim@sha256:b17334188d61b73352df79e2fc94f38ea92ed3982120dedd5fd614007cfebbef registry1.dso.mil/ironbank/opensource/debian/debian12/openjdk@sha256:bf1749f6e4b40dc7a08d5b8844eae0b56bc93073c105d770fa148fe2db60b456
All running on the same Debian 12.5 base image, and all produce the same failure (as expected).
I pulled the docker.io/library/debian:12.4 image from Docker, and it fails "apt update" with the same libgcrypt error. The docker.io/library/debian:12.5 image runs "apt update" just fine. Go figure...