Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

bib: use container based buildroot when building bootc disk images (HMS-3318) #138

Merged
merged 4 commits into from
Jan 25, 2024
Merged

bib: use container based buildroot when building bootc disk images (HMS-3318) #138

merged 4 commits into from
Jan 25, 2024

Commits on Jan 25, 2024

  1. bib: use container based buildroot when building bootc disk images 

    Instead of using the trandition rpm based buildroot this commit
switches the buildroot to the target bootc container. The rational
is that the low-level tooling like mkfs etc should match the target
system.
    @mvo5
    mvo5 committed Jan 25, 2024
    Configuration menu
    Copy the full SHA
    4db2d1c View commit details
    Browse the repository at this point in the history

  2. test: re-enable quay.io/centos-bootc/fedora-bootc:eln 

    This unbreak macos tests and also fedora-bootc:eln got fixed/reverted
upstream.
    @mvo5
    mvo5 committed Jan 25, 2024
    Configuration menu
    Copy the full SHA
    9752de9 View commit details
    Browse the repository at this point in the history

  3. tests: increase podman machine limits on macOS

    @mvo5
    mvo5 committed Jan 25, 2024
    Configuration menu
    Copy the full SHA
    f0eea67 View commit details
    Browse the repository at this point in the history

  4. bib: use the Linux runner for building disk images 

    Distro-specific runners try to set up a build environment to satisfy
certain expectations for stages (things they might expect from a live OS
environment).  One of the things the Fedora runner does is run
`systemd-tmpfiles --create`.  This causes a lot of warnings in our new
buildroot, like the following:

    /usr/lib/tmpfiles.d/rpm-ostree-autovar.conf:31: Failed to resolve user 'rpcuser': No such process

likely because we are running in an "ostree-based" tree that isn't fully
deployed (/etc/passwd only contains root).

The Linux runner is a fallback runner that doesn't perform any
preparations.  This should be adequate for the stages we use in bib.
    @achilleas-k
    achilleas-k committed Jan 25, 2024
    Configuration menu
    Copy the full SHA
    f9b3fbe View commit details
    Browse the repository at this point in the history