-
Notifications
You must be signed in to change notification settings - Fork 86
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
Demonstrate a debian or arch base image #865
Comments
If you need help testing anything, please let me know. I'm very interested in using |
I had some time on my hands this weekend and decided to have a look at building an Archlinux bootc container. Base ImageI started with building an OSTree repository for a arch-based rootfs and used M1cha's archlinux-ostree tooling for this. ./arch-ostree build_builder_container
./arch-ostree build_rootfs_container --rootfs-containerfile examples/Containerfile.minimal --rootfs-tag localhost/archlinux:rootfs
ostree init --repo=$(pwd)/ostree
./arch-ostree --ostree-repo $(pwd)/ostree commit_rootfs_container --rootfs-tag localhost/archlinux:rootfs -- -b minimal I did modify the I could use the OSTree repo to generate a base image using Custom packagesMaybe I find time to upload the bootc: This is just a simple bootupd: Same as fedora-boot: This one cobbles together everything from Fedora's RoadblocksThe following is pretty much arch-specific, however I'm sure a lot of aspects also apply to other distributions.
Of course all of this is mitigated by using Fedora's boot-related packages, but that certainly is only a workaround to get it running at all. |
Yes...sorry. There's some active discussion in coreos/bootupd#468 again about generalizing it.
That's...unfortunate indeed, though it's probably worth noting that there's been some long lingering conflict and the BLS that grub implements is not the same as the BLS type 1 as documented. Thanks for working on this! Bigger picture I was thinking about trying to make bootupd a soft dependency here. One thing that hurts is that bootloader bits are spread across both ostree and bootupd. This all said I am sure the thing that would help the most is for us to support systemd-boot. That is a long, longstanding TODO on the ostree side but brings up its own complexities. |
Let's do the work necessary to help push forward a Debian, Arch or other OS base image.
There are multiple components to this:
/ostree
ostreedev/ostree-rs-ext#674 will be extremely helpfulI would actually like to just execute on coreos/bootupd#432 soon to close the iteration loop.
The text was updated successfully, but these errors were encountered: