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.

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

compose: Allow missing repos key and add --source-root flag #5136

Merged
merged 2 commits into from
Oct 24, 2024

Conversation

jlebon
Copy link
Member

@jlebon jlebon commented Oct 23, 2024

Both of those are motivated by the fedora-bootc use case to clean up the container-native compose path. See individual commit messages.

Related: https://gitlab.com/fedora/bootc/tracker/-/issues/39

In fedora-bootc, we want the API to set the Fedora version to use to
be `--from quay.io/fedora/fedora:<N>`, from which the repo files are
copied. So in that case, we just want the default repos that are enabled
in that base image to be used. Support this use case in rpm-ostree by
just defaulting to that when `repos` is not specified.

Related: https://gitlab.com/fedora/bootc/tracker/-/issues/39
@cgwalters
Copy link
Member

This is including #5118 right?

@jlebon
Copy link
Member Author

jlebon commented Oct 23, 2024

This is including #5118 right?

Not quite. :) See #5118 (comment)

In fedora-bootc, we want the API to set the Fedora version to use to be
`--from quay.io/fedora/fedora:<N>`, from which the releasever is set.
Support this use case in rpm-ostree by adding a new `--source-root`
option to point libdnf at a different mount root to determine the
releasever. (See also previous commit.)

Related: https://gitlab.com/fedora/bootc/tracker/-/issues/39
@cgwalters
Copy link
Member

In your patches is it setting --source-root /?

@jlebon
Copy link
Member Author

jlebon commented Oct 23, 2024

In your patches is it setting --source-root /?

Not quite. You can see it in the last commit of https://gitlab.com/fedora/bootc/base-images/-/merge_requests/64 (well first commit I guess because Gitlab reverses the list).

https://gitlab.com/fedora/bootc/tracker/-/issues/39#note_2174172493 is the entrypoint for all these PRs BTW. Notably, this PR and https://gitlab.com/fedora/bootc/base-images/-/merge_requests/64 go together and are follow-ups to https://gitlab.com/fedora/bootc/base-images/-/merge_requests/63.

@cgwalters
Copy link
Member

cgwalters commented Oct 23, 2024

Ahhh right because we're separating the repos container and the builder container. Yeah, a reasonable general case but I could actually see an argument that we should encourage conflating them.

I think I'd like to have a nice high level --use-host-context or so but that can come later.

@cgwalters
Copy link
Member

Uh, no idea what's going on with that clang failure...just clicked retry

@jlebon
Copy link
Member Author

jlebon commented Oct 24, 2024

CI is broken on #5137. Just going to force this in.

@jlebon jlebon merged commit 842bb2a into coreos:main Oct 24, 2024
16 of 17 checks passed
@jlebon jlebon deleted the pr/repos-releasever branch October 24, 2024 19:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants