You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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.
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:
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 thepodman run
invocations for bib, allowing generic passthrough of everything there (e.g. could generate an ISO, qcow2 etc. without specifically running it)The text was updated successfully, but these errors were encountered: