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
openshift/origin docker container fails to start: failed to create kubelet: misconfiguration: kubelet cgroup driver: "systemd" is different from docker cgroup driver: "cgroupfs" #14766
Comments
Kubernetes overrides of the default cfgroups and set to systemd instead. On systems where systemd is not used, this is unfortunate. I compiled openshift origin again after commenting out line 79 in pkg/cmd/server/kubernetes/node/options/options.go ... and now for me docker and kubernetes are using cgroupfs again for me. Kubernetes does have a method to figure the docker cgroup driver in local-up-cluster.sh. But I don't know how everything is supposed to work together. |
I get the same error even on Fedora
|
Fedora is a frontrunner for SystemD, so if you have installed Docker using any of these methods, you should have a docker with a systemd cgroup driver. run "docker info" and your docker will show cgroupfs as cgroup driver. Probably you are better off reinstalling your docker using these instructions. Debian is more recently moving towards systemd, but it's optional. Alpine which I am running my openshift on, doesn't come with systemd. I have to patch the node_config. |
@janmg you are right. I had overridden the default system unit file to add a second runtime. And that causes dockerd to switch back to cgroup. Adding systemd explicitly fixes the issue. The unit file in my case, that works
|
|
can some one give me some advice to fix |
Same here.
Tried on following systems (
|
@nazarewk @chenray844 follow @mcastelino advice |
Ran into this exact issue tonight Running:
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
Attempting to run the Origin docker container using the command listed in the docs fails with the error in the title.
Version
N/A, haven't even gotten far enough for it to work
Steps To Reproduce
docker logs -f origin
and wait for output to finishCurrent Result
Expected Result
Container should start up without issues
Additional Information
lsb_release -a:
docker -v:
Full container logs:
The text was updated successfully, but these errors were encountered: