-
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
Failed to start minikube on Debian: memory.swap.max: permission denied: unknown. #10505
Comments
However, if I run with |
Dig up a little bit: After the start failure, I immediately check the docker and got:
If I then use
So the problem seems to be the docker container has been created, but somehow could not be started? |
Looks related to cgroups v2 (can you confirm?), so probably the same issue as: #10371 $ docker info | grep "Cgroup Version"
Cgroup Version: 1
WARNING: No swap limit support
WARNING: No blkio weight support
WARNING: No blkio weight_device support If indeed $ docker run --memory 256m --memory-swap 256m busybox echo Hello World
WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
Hello World |
Then the kubelet runs on the node, and there is no privileged node container. The kubelet might have similar issues with restricting memory, haven't checked. It's related to the Debian kernel having certain features disabled by default: |
@afbjorklund Thank you for you reply... I tried commands you mentioned and below are the outputs:
So the solution is to check the Cgroup version and make the parameter optional? It so, I can help make that change.... |
This issue appears to be a duplicate of #10371, do you mind if we move the conversation there? Ths way we can centralize the content relating to the issue. If you feel that this issue is not in fact a duplicate, please re-open it using Thank you for reporting this! |
Hello,
I tried to run the
minikube start
on my Debian machine and gotI tried to run
minikube delete --all
and restart my computer, but that problem remains.Below is the full log with '--alsologtostderr'
The text was updated successfully, but these errors were encountered: