-
I 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-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 and see if that works without any terrible hacks (like 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 -
InfluxDB
InfluxDB high-performance time series database. Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.
-
I 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-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 and see if that works without any terrible hacks (like 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 -
I 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-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 and see if that works without any terrible hacks (like 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 -
I think bootc is exactly what you're looking for. I use it[1] for configuration like you mentioned but also for:
- Installing codecs from third-party repositories. This is especially nice to do in CI because you get a build failure if packaging drift happens.
- Installing out-of-tree drivers. Again, you get a build failure in CI if an out-of-tree kernel module won't build. In addition, you can use multi-stage builds (see the Dockerfile in my repo for an example) to avoid pulling dependencies into your final system image. This saves me from having the 70 or so RPM packages that are required for building NVIDIA's drivers installed on my PC.
It's not quite as ambitious as NixOS but I think it gives a lot of the same benefits with far less effort.
[1]: https://github.com/averms/verms-os
