Re:Bottlerocket – Minimal, immutable Linux OS with verified ...
by xyzzy123 on Saturday September 23, 2023 @06:25PM
(#37628117)
To be fair, I think "VM" on the OS for Flatcar / BottleRocket / CoreOS is not a requirement in the same way as on RHEL etc. I appreciate this can cause difficulties in some regulated domains where your auditor might nonetheless force some useless activities on you because there's a "vm" box that needs to be ticked on the compliance worksheet.
Do you want to know if you are patched? Ok, well are you running the latest version? If so, you have all the available patches.
Most of the reason we need VM on a "traditional" OS is to handle the fact that they have a very broad configuration space and their software composition can be - and often is - pretty arbitrary (incorporating stuff from a ton of sources / vendors and those versions can move independently).
But that's not how you're supposed to use a container OS.
If you do "extra work" to discover vulnerabilities in "latest", you are not really doing the job of a system owner (whose job is mostly to apply latest patches from upstream in a timely fashion), you are doing the work of a security researcher.
Do you want to know if you are patched? Ok, well are you running the latest version? If so, you have all the available patches.
Most of the reason we need VM on a "traditional" OS is to handle the fact that they have a very broad configuration space and their software composition can be - and often is - pretty arbitrary (incorporating stuff from a ton of sources / vendors and those versions can move independently).
But that's not how you're supposed to use a container OS.
If you do "extra work" to discover vulnerabilities in "latest", you are not really doing the job of a system owner (whose job is mostly to apply latest patches from upstream in a timely fashion), you are doing the work of a security researcher.