Open bodand opened 1 month ago
I have noticed that I cannot use the artficats built by the Debian Docker image published on the ghcr.io
in the normal buster debian image. In reality, the published Debian image is more up-to-date.
The GraalVM image used is actually 24.1.0, unlike the source code that specifies 24.0.2, and the Debian base image is apparently 20240917
. The libc of the published image has a different ABI, and the repositories include libssl3
, which is absent from the actual debian-buster
repositories. The reason is that they override the base and versions using ARG
.
@brahimhaddou Can you provide the full source code and arguments for the published images?
https://github.com/graalvm/container/blob/d65dc5d56f034bc7323cc5e67126bad6e7f29238/truffleruby-community/Dockerfile.debian#L17 https://github.com/graalvm/container/blob/d65dc5d56f034bc7323cc5e67126bad6e7f29238/truffleruby-community/Dockerfile.debian#L6
vs
Huh, it really isn't. I, for some reason, didn't bother to check the actual container.
I was reading this https://github.com/graalvm/container/blob/master/truffleruby-community/README.md, and it said Debian 10, at which point I suspected it was the docs that was out of sync with the broader universe, as it has the tendency to, so I looked at the Dockerfile which also had buster. At this point I decided that it is what must be...
Running:
docker run -it --rm ghcr.io/graalvm/truffleruby-community:24.1.0-debian-20240917 cat /etc/os-release
Produces
PRETTY_NAME="Debian GNU/Linux trixie/sid"
NAME="Debian GNU/Linux"
VERSION_CODENAME=trixie
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
Which is quite different from buster, so it's not the images that are not up to date, just the docs. A considerably better situation.
Yes, I can confirm that it is debian:sid-slim
I might have missed the reasoning if it is explained somewhere, but I'm just going to ask instead of looking around more.
The Debian base for (at least) TruffleRuby is Debian 10 (Buster) which is EOL, and only supported by ELTS. Is there a reason this is used for the Debian images, and if possible can it be updated to oldstable (11 Bullseye) or even stable (12 Bookworm)?