Wednesday, 2025-09-10

mnasiadkaJonathanWright[m]: tried to find the x86-64-v2 packages - and it seems you guys build it only for Kitten? (https://wiki.almalinux.org/development/almalinux-os-kitten-10.html#how-is-almalinux-os-kitten-different-from-centos-stream)15:31
sean-k-mooneyim not that famialr but i suspect that alma 9 was excluivle built for x86-64-v217:02
sean-k-mooneymnasiadka: were you hoping to use them for a diffent disto/release?17:03
mnasiadkasean-k-mooney: no, Kitten seems to be Alma’s ,,Stream’’ - that’s why I’m asking17:05
sean-k-mooneyso it was there beta before the 10 stabel release17:05
sean-k-mooneyand i guess there integration line17:06
sean-k-mooneyhttps://repo.almalinux.org/almalinux/10/cloud/x86_64_v2/images/AlmaLinux-10-GenericCloud-10.0-20250528.0.x86_64_v2.qcow217:07
sean-k-mooneyis the cloud ima g i currently use but i tought that was the stable relase not kitten17:07
sean-k-mooneybut i have not really looked at it closly17:07
mnasiadkaMight be I’m blind and we only need to use some v2 repos in container that we use in DIB - but there’s no easily findable documentation17:08
sean-k-mooneyhttps://repo.almalinux.org/almalinux/10/BaseOS/x86_64_v2/os/Packages/17:09
sean-k-mooneythey have teh rpms there too17:09
sean-k-mooneymnasiadka: its possibel thy do not have a v2 container base image17:09
sean-k-mooneymnasiadka: although they shoudl https://github.com/AlmaLinux/container-images/blob/2f239bc800a366ea4dc42378905c237ae6e4e03a/default/amd64_v2/Dockerfile17:10
sean-k-mooneymaybe you need to use a differnt tag17:10
sean-k-mooneymy best guess is that the image exists but the automation to tage it does not17:15
JonathanWright[m]There are x86_64_v2 builds for 10 and kitten 10.  9 was only pinned to v2 (not v3) so it doesn't need special builds there.17:23
JonathanWright[m]We do have a v2 base image but it's tricky to find because dockerhub and quay aren't really built to deal with different ISAs of a common architecture.17:24
sean-k-mooneyJonathanWright[m]: i think the issue is its not clear if the v2 iamges are built and pushed to https://hub.docker.com/_/almalinux/tags17:24
JonathanWright[m]They are, and there's a way to pull it.  Let me find the command.17:24
JonathanWright[m]Correct, v2 only exists on quay because docker hub doesn't support variations of a common base ISA.17:25
sean-k-mooneyah17:25
JonathanWright[m]docker run -it --rm --platform linux/amd64/v2 quay.io/almalinuxorg/almalinux:10 /bin/bash17:25
JonathanWright[m]note the extra /v2 on the end of platform17:25
JonathanWright[m]s/Correct/Correction/17:26
mnasiadkaOk, that might require some quirks in diskimage-builder, but at least I know the path17:27
sean-k-mooneyJonathanWright[m]: the other way around that although proably less correct is to add -v2 to the tag17:28
sean-k-mooneyplathform is proably more correct17:28
JonathanWright[m]I think that might be a workaround for dockerhub, yeah17:28
JonathanWright[m]But we've just pushed people to quay for it17:29
sean-k-mooneyso that is also why there are 2 amd64 variants right https://quay.io/repository/almalinuxorg/10-base?tab=tags17:29
JonathanWright[m]I don't see two variants?17:30
JonathanWright[m]do you mean 10.0 and 10 ?17:30
sean-k-mooneyi mean for any given tag https://quay.io/repository/almalinuxorg/10-base/manifest/sha256:926e495c38418bcac4500f67c91def1b6062cd5e7a7f48be77327abfd8f4552817:31
sean-k-mooneyare are 2 entires for amd64 and 1 for the other architectures17:31
JonathanWright[m]oh yes most likely.  quay.io isn't playing nice for me right now so I can't see the GUI (link you sent is busted on my end)17:31
sean-k-mooneyi was tryign to see if for any given tag the gui actully would let you know which to use17:32
JonathanWright[m]ok got it to work in a private tab, go figure.  yes.17:32
JonathanWright[m]This goes back to quay...kinda sorta supporting it.  Behind the scenes it does, but the GUI doesn't differentiate the two unfortunately17:32
JonathanWright[m]I think it will always pull the v3/default build unless you specify v217:33
sean-k-mooneyya it proably woudl be vhisable in the image metadata and or via the cli/api17:33
sean-k-mooneyi guess maybe one suggestion17:34
fungii'm not all that active in reviewing dib changes, but if it needs adjustments to support pulling container images from quay then i'm happy to review the changes enabling that17:34
sean-k-mooneyit might be good to add an exampel fo  --platform linux/amd64/v2 somewhere discoverable17:34
sean-k-mooneyperhaps in the description of the image on quay.io17:34
JonathanWright[m]I totally agree.  at first we weren't even planning on container images for v2...but demand has been overwhelming (similar story for cloud images).  We need to increase documentation around it17:35
sean-k-mooneymnasiadka: if you dont make progress on the contienr based approch you could try the older cloud image approch. the centos elemnt still use that https://github.com/openstack/diskimage-builder/blob/master/diskimage_builder/elements/centos/root.d/10-centos-cloud-image17:37
sean-k-mooneyyou could proably jsut overied the varibale and point it at the v2 alma  image to get something working17:38
sean-k-mooneyalthough i woudl not use that element direclty because it will messs up the repo config ecta17:38
sean-k-mooneybut the root.d part likley could be used in a new alma elemnt17:39
sean-k-mooneyoh never mind you alrady have one for 9 https://github.com/openstack/diskimage-builder/tree/master/diskimage_builder/elements/almalinux-container17:39
sean-k-mooneymnasiadka: https://docs.docker.com/build/building/multi-platform/#cross-compilation look like you can add the platform line in the from statement17:41
mnasiadkaYes, only the containerfile element needs platform passing support and we should be good17:41

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!