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

support bootc-image-builder #4

Open
cgwalters opened this issue Apr 22, 2024 · 2 comments
Open

support bootc-image-builder #4

cgwalters opened this issue Apr 22, 2024 · 2 comments

Comments

@cgwalters
Copy link
Contributor

https://gitlab.com/bootc-org/podman-bootc-cli/-/issues/26

Let's support a wrapper for https://github.com/osbuild/bootc-image-builder

This would first leverage CentOS/centos-bootc#453 to find the relevant image.

Also with this we should support being passed a config.

I'm envisioning:

podman-bootc run --via-bib

to start to do the disk image install that way to make it ergonomic to test. And that would happen automatically if passed podman-bootc run --image-config /path/to/config.json.

It'd also make sense to have
podman-bootc build-disk just be a direct wrapper for the podman run invocations for bib, allowing generic passthrough of everything there (e.g. could generate an ISO, qcow2 etc. without specifically running it)

@vrothberg
Copy link
Member

I think a wrapper for building disk images would be a huge in improve in UX. I am incapable to recall all the flags required for building a disk image (via podman run --tons-of-flags).

One thing to think about is which BIB image podman bootc would use. Would it always use :latest or be tied to a specific release? There are pros and cons for both I guess. It would be great to have the image be configurable.

@cgwalters
Copy link
Contributor Author

One thing to think about is which BIB image podman bootc would use

See CentOS/centos-bootc#453 which aimed to standardize this

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

No branches or pull requests

2 participants