The task currently uses Debian 11 Bullseye, which will be EOL in ~2024-07, according to https://wiki.debian.org/DebianReleases#Production_Releases
So it would be good to bump either now or latest in 6 months.
Ideally the ARM CI task uses the version of GCC that guix uses to cross compile, which is currently GCC 10 and Debian Bookworm ships with GCC 12, so I'll leave this in draft for now. See also https://packages.debian.org/bookworm/gcc-arm-linux-gnueabihf
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline for information on the review process. A summary of reviews will appear here.
Trying to move this to #27897 (comment)
Haven't digged deeper, but this seems to fix a bug for me as well, running the CI in podman on aarch64:
this pull: :heavy_check_mark: pass master:
Creating debian:bullseye container to run in
++ DOCKER_BUILDKIT=1
++ retry -- docker build --file /root/b-c-ci/ci/test_imagefile --build-arg CI_IMAGE_NAME_TAG=debian:bullseye --build-arg FILE_ENV=./ci/test/00_setup_env_arm.sh --tag=ci_arm_linux /root/b-c-ci
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
STEP 1/6: FROM debian:bullseye
STEP 2/6: ARG FILE_ENV
--> Using cache b7f8af530f9dc24beb2c614f74c3fc1e2fdc68e36671d3a4a4909b110ad5639b
--> b7f8af530f9d
STEP 3/6: ENV FILE_ENV=${FILE_ENV}
--> Using cache 4f07fb10abcd88b1135e1a4420fe3d7f1e721958ee44992316cc52fe5bb35feb
--> 4f07fb10abcd
STEP 4/6: COPY ./ci/retry/retry /usr/bin/retry
--> Using cache bc82f527cba0d4e6562fdd22b8c7d3d79eb9f738b9f313e56b521c919a7ee81f
--> bc82f527cba0
STEP 5/6: COPY ./ci/test/00_setup_env.sh ./${FILE_ENV} ./ci/test/01_base_install.sh /ci_base_install/ci/test/
--> Using cache 46acb929ededa7444186fdb039efc14668f4aa28ec3230acefa1061734594431
--> 46acb929eded
STEP 6/6: RUN ["bash", "-c", "cd /ci_base_install/ && set -o errexit && source ./ci/test/00_setup_env.sh && ./ci/test/01_base_install.sh"]
--> Using cache 53923143aba9666c9fce02249416f5d94c83b17b0b46cee6e1fc4a0eafc517e8
COMMIT ci_arm_linux
--> 53923143aba9
Successfully tagged localhost/ci_arm_linux:latest
53923143aba9666c9fce02249416f5d94c83b17b0b46cee6e1fc4a0eafc517e8
++ docker volume create ci_arm_linux_ccache
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: volume with name ci_arm_linux_ccache already exists: volume already exists
++ true
++ docker volume create ci_arm_linux_depends
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: volume with name ci_arm_linux_depends already exists: volume already exists
++ true
++ docker volume create ci_arm_linux_previous_releases
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: volume with name ci_arm_linux_previous_releases already exists: volume already exists
++ true
++ '[' -n '' ']'
+++ docker run --rm --interactive --detach --tty --mount type=bind,src=/root/b-c-ci,dst=/ro_base,readonly --mount type=volume,src=ci_arm_linux_ccache,dst=/root/b-c-ci/ci/scratch/.ccache --mount type=volume,src=ci_arm_linux_depends,dst=/root/b-c-ci/depends --mount type=volume,src=ci_arm_linux_previous_releases,dst=/root/b-c-ci/releases/arm-linux-gnueabihf -w /root/b-c-ci --env-file /tmp/env --name ci_arm_linux ci_arm_linux
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: crun: executable file `bash` not found in $PATH: No such file or directory: OCI runtime attempted to invoke a command that was not found
++ CI_CONTAINER_ID=