Kai Lüke
Kai Lüke
From my observation it's often possible to cut things down a bit but yes, at some point we hit a limit. Without a limit one can easily bloat everything and...
Here is the report against the previous nightly: [image-diff.txt](https://github.com/flatcar/Flatcar/files/14615127/image-diff.txt) And against the previous Alpha: [image-diff-alpha.txt](https://github.com/flatcar/Flatcar/files/14615148/image-diff-alpha.txt)
> Here is the report against the previous nightly: [image-diff.txt](https://github.com/flatcar/Flatcar/files/14615127/image-diff.txt) And against the previous Alpha: [image-diff-alpha.txt](https://github.com/flatcar/Flatcar/files/14615148/image-diff-alpha.txt) Maybe `tpm2` in the initrd could be loaded from `/sysusr`? Something also started to...
With the "minimal first stage" initrd to load and switch to the full initrd we have 30 MB used now and can double the size again with updates/features but we...
Thanks, the runc PR looks close to land, and since Docker 25 doesn't block on the runc release we can already start updating Docker to have everything in place once...
I think we can also build runc with 1.21 and let kola check if we have any issues (The readme says `runc only supports Linux. It must be built with...
In the github action we can fetch the active k8s versions from https://raw.githubusercontent.com/kubernetes/website/main/data/releases/schedule.yaml and filter out releases with a target date in the future (using `next:` as first try, otherwise...
It seems that the error can also lead to the boot not finding the OEM partition. When encountering, what did you do to get a correct build? Did it involve...
For me the error went away after also emerging the coreos-modules again plus to be sure coreos-kernel and then building the image.
> For me the error went away after also emerging the coreos-modules again plus to be sure coreos-kernel and then building the image. Seems that this doesn't always help and...