particle-os/debian-bootc-base-images
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Containerfile: explain why REPOS_IMAGE is needed

Browse source 
Having this is a bit confusing because the use case for it is exactly
what `podman build --from` was intended for. Let's add a comment here
about why it was added in aa9c6c2 [1], which is because konflux doesn't
support --from yet [1].

[1] https://gitlab.com/fedora/bootc/base-images/-/merge_requests/106#note_2380147640
This commit is contained in:
Dusty Mabe 2025-04-29 15:25:22 -04:00
parent b251e1cbb3
commit ebaedc73ed
No known key found for this signature in database
GPG key ID: 3302DBD73952E671
1 changed files with 3 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

3
Containerfile
View file

@ -9,6 +9,9 @@
# Override this repos container to control the base image package versions. For
# example, podman build --from=quay.io/fedora/fedora:41 will get you a system
# that uses Fedora 41 packages. Or inject arbitrary yum repos (COPR, etc) here.
#
# Note we also support --build-arg REPOS_IMAGE=quay.io/fedora/fedora:41 here
# since konflux doesn't yet support --from.
ARG REPOS_IMAGE=quay.io/fedora/fedora:rawhide
FROM $REPOS_IMAGE as repos