search

toolbx-images / images

Community maintained container images to use with toolbx and distrobox
https://containertoolbx.org/
Apache License 2.0
342 stars 30 forks source link

github/workflows/centos: Also push zstd:chunked compressed images #129

Open travier opened 4 months ago

travier commented 4 months ago

github/workflows: Use Ubuntu 24.04 runners

github/workflows/centos: Also push zstd:chunked compressed images

See: https://github.com/toolbx-images/images/issues/128 See: https://fedoraproject.org/wiki/Changes/zstd:chunked See: https://docs.podman.io/en/latest/markdown/podman-push.1.html#compression-format-gzip-zstd-zstd-chunked See: https://github.com/coreos/fedora-coreos-tracker/issues/1660

travier commented 4 months ago

CC @castrojo :)

travier commented 4 months ago

Let's test this format with one image first and then copy it for all the others.

travier commented 4 months ago 
Processing triggers for libc-bin (2.31-13+deb11u10) ...
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault (core dumped)
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault (core dumped)
dpkg: error processing package libc-bin (--configure):
 installed libc-bin package post-installation script subprocess returned error exit status 139
Processing triggers for ca-certificates (20210119) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Processing triggers for dbus (1.12.28-0+deb11u1) ...
Processing triggers for libgdk-pixbuf-2.0-0:arm64 (2.42.2+dfsg-1+deb11u2) ...
Errors were encountered while processing:
 libc-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)
Error: building at STEP "RUN apt-get update &&     DEBIAN_FRONTEND=noninteractive apt-get -y install         libnss-myhostname         $(cat extra-packages | xargs) &&     rm -rd /var/lib/apt/lists/*": while running runtime: exit status 100

😞

castrojo commented 4 months ago

Thanks for the tag! cc @p5

One thing I learned is that many tutorials recommend ubuntu-latest, which is currently pointing to 22.04, so when I turned this on someone immediately filed an issue since their downstream build broke due to the old podman version in 22.04.

The github public roadmap mentions that 24.04 builders should go out of beta this summer, so we figured it would just be best to roll it out the day after those go live or something after confirming that ubuntu-latest is pointing to 24.04.