-
Notifications
You must be signed in to change notification settings - Fork 706
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
kubeadm init preflight check error - cannot unmarshal number into Go value of type bool #231
Comments
If it helps. I can confirm this is happening. I have also confirmed your fix of adding Update: |
I was able to workaround this by installing the below docker version and running yum install kubelet kubeadm kubectl kubernetes-cni
|
I'm facing the exact same issue
|
I do not see this running 1.6.4 on CentOS 7.3 with Docker 1.12.6 Can you repro on this stack ^ ? |
I switched to Docker 1.12.6 as mentioned and got rid of preflight check
and I'm running the following kubelet and Linux version
But now its stuck at 'control plane to become ready.
and I'm certain that I've disabled selinux |
@jazemzer That seems like a (separate) proxy issue. Please open a new issue and give more details. I think this is a docker issue, maybe specific to v1.12.2? |
Yes, this issue is specific to Docker version < v1.12.2. It actually works on 1.12.2. I can close the issue if you want. |
Is this a BUG REPORT or FEATURE REQUEST?
BUG REPORT
Versions
kubeadm version (use
kubeadm version
): kubeadm version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.1", GitCommit:"b0b7a323cc5a4a2019b2e9520c21c7830b7f708e", GitTreeState:"clean", BuildDate:"2017-04-03T20:33:27Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}Environment:
kubectl version
):Client Version: version.Info{Major:"1", Minor:"6", GitVersion:"v1.6.1", GitCommit:"b0b7a323cc5a4a2019b2e9520c21c7830b7f708e", GitTreeState:"clean", BuildDate:"2017-04-03T20:44:38Z", GoVersion:"go1.7.5", Compiler:"gc", Platform:"linux/amd64"}uname -a
): Linux jcia9362 4.1.12-61.1.24.el7uek.x86_64 kubeadm init starts paused containers on ubuntu 16.04 #2 SMP Wed Jan 4 14:05:13 PST 2017 x86_64 x86_64 x86_64 GNU/LinuxWhat happened?
Error encountered during kubeadm init and stops
Error message is
What you expected to happen?
kubeadm init should proceed without issues
How to reproduce it (as minimally and precisely as possible)?
Followed these steps to install and configure kubeadm
Anything else we need to know?
added --cgroup-driver=systemd and commented network args and tried after systemctl daemon-reload
I'm able to initialize and setup kubeadm on another VMWare virtual machine with this OS specs
CentOS Linux release 7.3.1611 (Core)
Linux kubeadmmaster 3.10.0-514.10.2.el7.x86_64 #1 SMP Fri Mar 3 00:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: