[RFE] Documentation around available sysext must be clearer - Githubissues

flatcar / Flatcar

Flatcar project repository for issue tracking, project documentation, etc.

https://www.flatcar.org/

Apache License 2.0

653 stars 27 forks source link

[RFE] Documentation around available sysext must be clearer #1476

Open tormath1 opened 1 week ago

tormath1 commented 1 week ago

Current situation

Flatcar provides three types of systemd-sysext images:

non-official: from the Flatcar sysext-bakery releases
official: like ZFS, Podman or Python (one needs to write the extension name in /etc/flatcar/enabled-sysext.conf)
built-in: like Docker, Containerd, OEM partition

But the difference is not very clear from a user point of view.

Impact

It's confusing to know which sysext is available / built-in / etc. For example there is a Docker image from the bakery but there is also a Docker built-in sysext image. (read: https://github.com/flatcar/Flatcar/issues/1470 or https://github.com/flatcar/Flatcar/issues/1481)