Consumption/updates of user-supplied software from the sysext-bakery or built from the SDK
No due date
40% complete
- Publish built images in sysext-bakery with GitHub Action as GitHub releases, incl. manifest file for systemd-sysupdate (use upstream binaries where possible and only compile if required)
- Add docs for systemd-sysupdate
- Add more build recipes for common cases (runwasi shims, upstream containerd binaries, Kubernetes/CAPI [see PoC issue])
- Improve build_sysex…
- Publish built images in sysext-bakery with GitHub Action as GitHub releases, incl. manifest file for systemd-sysupdate (use upstream binaries where possible and only compile if required)
- Add docs for systemd-sysupdate
- Add more build recipes for common cases (runwasi shims, upstream containerd binaries, Kubernetes/CAPI [see PoC issue])
- Improve build_sysext SDK tool to have a generic manglefs script that moves entries under /etc/systemd/ to /usr/ and creates a helper service unit that creates directories under /etc and /var and sets up symlinks for config files in there, and runs before other units of this sysext will run
- SDK: build support for distro-independent sysexts (custom paths) in SDK (based on Gentoo prefix)
- sysext-bakery: Add build helper based on Nix as alternative to the Gentoo prefix/static binaries because it’s a very common tool for self-contained software trees
- upstream systemd: run systemd-sysupdate from initrd to download images instead of having to supply them from ignition (or do an extra reboot)