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] Upgrade systemd 255 to systemd 256 #1501

Open
2 tasks
ader1990 opened this issue Jul 24, 2024 · 1 comment · May be fixed by flatcar/scripts#2145
Open
2 tasks

[RFE] Upgrade systemd 255 to systemd 256 #1501

ader1990 opened this issue Jul 24, 2024 · 1 comment · May be fixed by flatcar/scripts#2145
Labels
kind/feature A feature request

Comments

@ader1990
Copy link

ader1990 commented Jul 24, 2024

Current situation

Currently, Flatcar uses systemd 255 and the usual historical cadence of a systemd version is one every 6 months, and for Flatcar is of around 1-2 years.

Opening this issue to track possible blockers for the 255 -> 256 upgrade early, as there might be the need of structural changes to the Flatcar layout and how to's, as systemd is a cornerstone critical package for Flatcar, along with the kernel, ignition and containerd (k8s).

Also, the mutable sysext / confext patches for 255 that we currently have already borrow functionality from 256.

Ideal future situation

Upgrade to systemd version 256.

Current blockers:

  • ignition-setup.service fails to run because /usr is now read only
  • Systemd 256 marks the system as tainted is /usr/bin is not symlinked to /usr/sbin (systemd: system is tainted: unmerged bin)
@ader1990 ader1990 added the kind/feature A feature request label Jul 24, 2024
@ader1990 ader1990 linked a pull request Jul 24, 2024 that will close this issue
2 tasks
@ader1990
Copy link
Author

Unmerged bin blocker is currently in progress of being solved: flatcar/scripts#2068

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature A feature request
Projects
Status: 📝 Needs Triage
Development

Successfully merging a pull request may close this issue.

1 participant