4 ms·
Sorry mate, I didn't mean to say that you're not part of said community. I have seen that there are instructions here for arch: https://github.com/bootc-dev/b
by worthless-trash 2y ago
Sorry mate, I didn't mean to say that you're not part of said community.
I have seen that there are instructions here for arch:
https://github.com/bootc-dev/bootc/issues/865#issuecomment-2526413033 https://github.com/bootc-dev/bootc/issues/865#issuecomment-2...
I do see that the poster mentions that "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."
If you're interested, I can talk to the bootc team to document what needs to be done and how it can be more clearly stated. Do you know rust enough to get involved if i can convince the group to get the party started ?
- yjftsjthsd-h 2y agoI don't know rust. I had assumed that all that was needed was to feed bootc-image-builder an image with files in the right places and it should work; if it needs to actually run native code (not just call a shell script or something) to integrate with the package manager, then it's over my head. And... also that seems like an overly-tightly-coupled design, IMHO. Hopefully https://github.com/coreos/bootupd/issues/468#issuecomment-1555962793 https://github.com/coreos/bootupd/issues/468#issuecomment-15... (and similar) is the path forward. I guess I will see if I can get my head around https://github.com/frap129/arch-bootc https://github.com/frap129/arch-bootc and see if that works without any terrible hacks (like https://github.com/bootc-dev/bootc/issues/865#issuecomment-2526413033 https://github.com/bootc-dev/bootc/issues/865#issuecomment-2... talking about hacking the code to replace rpm with pacman), and then assuming I don't loose steam I can write something on the relevant issue(s) outlining exactly what does work and doesn't work how to reproduce it (because currently someone even trying to see what the current state of things looks like has to navigate through several layers of pages and can still walk away uncertain). My vague plan is [x] try building a qcow2 image from quay.io/centos-bootc/centos-bootc:stream9 [x] try building a lightly modified container image from centos stream and turn that into a qcow2 [ ] try building frap129's archlinux image [ ] write up minimal steps to reproduce frap129's archlinux image and boot it in qemu [ ] try building a debian image [ ] try building an alpine image [ ] try building a postmarketos image (my actual original goal) and either leave a trail of documentation of how to do things that do work, or else write up exactly what breaks.
- worthless-trash 2y agoExcellent, i'm sure that maybe even if you get stuck, we can encourage/get help from the bootc people to get the ball rolling again. There seems to be a pretty big push for bootc internal to Red Hat and from my limited experience the team is helpful. Do you have a blog where you are recording your status ?
- yjftsjthsd-h 2y agoNow I do:P (Honestly, a good idea, and a good excuse to get my blog working again even if it is clunky.) https://brianecole.com/blog/2025-03-27_bootc-initial.html https://brianecole.com/blog/2025-03-27_bootc-initial.html https://brianecole.com/blog/2025-03-27_bootc-movingarch.html https://brianecole.com/blog/2025-03-27_bootc-movingarch.html Although the more useful thing will be chiming in on github issues. I'll do that next.
- worthless-trash 2y agoSubscribed.
- worthless-trash 2y agoI just noticed one update to https://github.com/bootc-dev/bootc/issues/865 https://github.com/bootc-dev/bootc/issues/865 It looks as though, fnzr has been able to get past the 'dnf' requirements (I dont know arch, but I assume pacman is an rpm/dnf equivalent).