Replies: 1 comment 2 replies
-
@p5 multiple people have done prototypes like these. For the time being, Wolfi maintainers are not comfortable to put a kernel into wolfi-dev/os. Largely due to the weight of expectations that will be upon us w.r.t. LSM, secureboot, dkms, and userspace packages not working as the host-os. Afterall Wolfi is a containers-first OS. There are lots of subtle things missing or miss-configured all over wolfi, which may make host-os experience not very straightforward. Also do think carefully about data management, none of the packages assume upgrade; and many of them do not support upgrades. No support is provided, but to freshly install/unpack packages (with either apk-tools or apko). note you don't have to build your own kernel, there are multiple providers of upstream kernel builds which are good enough. For example Zabbly kernel builds. There is also Fedora ARK and I thought they published binary builds somewhere but cannot find it. Putting a kernel into wolfi is currently out of scope; but if you have any feedback, bug reports, or fixes to packages to make them work better outside of containers - and if they are simple enough, we will consider integrating them. |
Beta Was this translation helpful? Give feedback.
-
I have been following the https://github.com/containers/bootc development, and had a crazy idea. Theoretically we can build and boot a bare-metal system using only wolfi-os (and custom melange) packages. This allows us to generate complete SBOMs of an entire OS, and have the same "zero CVEs" as we do in container images.
I am in no way expecting Chainguard to pick this up as supported. I thought it would be a cool project to showcase both tools.
Has anybody been able to work out the correct configuration to get a Linux Kernel package building? I've been looking into it for the past hour-ish and have made progress, though said progress is slowing down when I reached the linux internals.
Beta Was this translation helpful? Give feedback.
All reactions