Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
tormath1 opened this issue Jun 21, 2024 · 1 comment · Fixed by flatcar/flatcar-website#348
Closed

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

tormath1 opened this issue Jun 21, 2024 · 1 comment · Fixed by flatcar/flatcar-website#348
Labels
good first issue Get started with Flatcar contribution with this issue. kind/docs kind/feature A feature request

Comments

@tormath1
Copy link
Contributor

tormath1 commented Jun 21, 2024

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: #1470 or #1481)

@krishjainx
Copy link

PR #348 to flatcar-website should help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Get started with Flatcar contribution with this issue. kind/docs kind/feature A feature request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants