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

Warning when folks using default SystemdCgroup (false) when running in Systemd environments #8063

Closed
dims opened this issue Feb 7, 2023 · 1 comment
Assignees
Labels
area/cri Container Runtime Interface (CRI)

Comments

@dims
Copy link
Member

dims commented Feb 7, 2023

Folks,

We've had folks run into this situation quite a few times:
kubernetes/kubernetes#115581 (comment)

Essentially the default in our config.toml in containerd for SystemdCgroup is false and most of k8s has been the opposite (example kubernetes/kubeadm#2376)

So would we may be at least add a warning in our logs that systemd is ON and their config is NOT reflecting that?

Note there's a handy IsRunningSystemd we can use to check and log a message: https://cs.k8s.io/?q=IsRunningSystemd&i=nope&files=&excludeFiles=&repos=kubernetes/kubernetes

thanks!

@AkihiroSuda AkihiroSuda added the area/cri Container Runtime Interface (CRI) label Feb 8, 2023
@carlory
Copy link

carlory commented Jun 6, 2023

/assign

@dosubot dosubot bot added the Stale label Aug 1, 2024
@dosubot dosubot bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 7, 2024
@dosubot dosubot bot removed the Stale label Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/cri Container Runtime Interface (CRI)
Projects
None yet
Development

No branches or pull requests

3 participants