-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Kubelet: misconfiguration: kubelet cgroup driver: "'systemd'" is different from docker cgroup driver: "systemd" #6544
Comments
cgroup-driver
option
I think this is a generic bug with the docker --format, where I copied the code from.
We don't need extra quotes, when we are running c := exec.Command("docker", "version", "--format", "'{{.Server.Version}}'") c := exec.Command("docker", "info", "--format", "'{{.CgroupDriver}}'") Unfortunately we don't have any centos test machines yet (#3552) |
Unfortunately the unit test was doctored to match the expected output, not reality. Slightly odd that nobody has complained about the extra quotes in the version... |
Note that Kubernetes ( driver, err := kubeadmutil.GetCgroupDriverDocker(opts.execer)
if err != nil {
klog.Warningf("cannot automatically assign a '--cgroup-driver' value when starting the Kubelet: %v\n", err)
} else {
kubeletFlags["cgroup-driver"] = driver
} And then fails to detect the default driver for any other container runtime, even though doc says so. // TODO: add support for detecting the cgroup driver for CRI other than
// Docker. Currently only Docker driver detection is supported:
// Discussion:
// https://github.com/kubernetes/kubeadm/issues/844 Since v1.14.0, kubeadm will try to automatically detect the container runtime on Linux nodes by scanning through a list of well known domain sockets. So even when we pass in a totally bogus value for docker, we still get a valid kubelet config...
There's too many stupid docker hacks present still, would be much better if it started to use CRI ? |
@zigarn : Thanks for reporting, hopefully fixed in |
I confirm that the problem is solved in Thanks everyone for the great reactivity and quick fixing release! |
The exact command to reproduce the issue:
The full output of the command that failed:
The output of the
minikube logs
command:Main problem:
There are simple quotes around the
cgroup-driver
option.The operating system version:
CentOS Linux release 7.6.1810 (Core)
The text was updated successfully, but these errors were encountered: