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

kubeadm fails at HEAD w/ Kubernetes 1.10 & 1.11: unsupported docker version: 18.09.6 #4304

Closed
tstromberg opened this issue May 21, 2019 · 5 comments · Fixed by #4306
Closed
Assignees
Labels
area/kubernetes-versions Improving support for versions of Kubernetes good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@tstromberg
Copy link
Contributor

tstromberg commented May 21, 2019

HEAD now defaults to Docker 18.09. Because of this, we should turn off the Docker verification check for v1.10.x (preferred), or drop support for v1.10.x

Command:

make out/minikube; ./out/minikube start --vm-driver=virtualbox --kubernetes-version=v1.10.13

Output:

💣  Error starting cluster: kubeadm init: 
sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml  --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data-minikube --ignore-preflight-errors=Port-10250 --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap --ignore-preflight-errors=CRI 

[init] Using Kubernetes version: v1.10.13
[init] Using Authorization modes: [Node RBAC]
[preflight] Running pre-flight checks.
[preflight] The system verification failed. Printing the output from the verification:
KERNEL_VERSION: 4.15.0
CONFIG_NAMESPACES: enabled
CONFIG_NET_NS: enabled
CONFIG_PID_NS: enabled
CONFIG_IPC_NS: enabled
CONFIG_UTS_NS: enabled
CONFIG_CGROUPS: enabled
CONFIG_CGROUP_CPUACCT: enabled
CONFIG_CGROUP_DEVICE: enabled
CONFIG_CGROUP_FREEZER: enabled
CONFIG_CGROUP_SCHED: enabled
CONFIG_CPUSETS: enabled
CONFIG_MEMCG: enabled
CONFIG_INET: enabled
CONFIG_EXT4_FS: enabled
CONFIG_PROC_FS: enabled
CONFIG_NETFILTER_XT_TARGET_REDIRECT: enabled (as module)
CONFIG_NETFILTER_XT_MATCH_COMMENT: enabled (as module)
CONFIG_OVERLAY_FS: enabled (as module)
CONFIG_AUFS_FS: not set - Required for aufs.
CONFIG_BLK_DEV_DM: enabled
DOCKER_VERSION: 18.09.6
OS: Linux
CGROUPS_CPU: enabled
CGROUPS_CPUACCT: enabled
CGROUPS_CPUSET: enabled
CGROUPS_DEVICES: enabled
CGROUPS_FREEZER: enabled
CGROUPS_MEMORY: enabled
	[WARNING Service-Kubelet]: kubelet service is not enabled, please run 'systemctl enable kubelet.service'
	[WARNING Service-Docker]: docker service is not enabled, please run 'systemctl enable docker.service'
Flag --admission-control has been deprecated, Use --enable-admission-plugins or --disable-admission-plugins instead. Will be removed in a future version.
[preflight] Some fatal errors occurred:
	[ERROR SystemVerification]: unsupported docker version: 18.09.6
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`

Related: #4180 and #3323

@tstromberg
Copy link
Contributor Author

Looks like v1.11.10 is also affected, so in keeping with our current policy of trying to support the last 5 minor versions, I'd rather workaround this than solve it by dropping support for older Kubernetes versions if possible.

@tstromberg tstromberg changed the title HEAD w/ Kubernetes 1.10.13: [ERROR SystemVerification]: unsupported docker version: 18.09.6 HEAD w/ Kubernetes 1.10 & 1.11: [ERROR SystemVerification]: unsupported docker version: 18.09.6 May 21, 2019
@tstromberg tstromberg changed the title HEAD w/ Kubernetes 1.10 & 1.11: [ERROR SystemVerification]: unsupported docker version: 18.09.6 kubeadm fails at HEAD w/ Kubernetes 1.10 & 1.11: unsupported docker version: 18.09.6 May 21, 2019
@tstromberg tstromberg added this to the v1.1.0 milestone May 21, 2019
@tstromberg tstromberg added area/kubernetes-versions Improving support for versions of Kubernetes priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels May 21, 2019
@afbjorklund
Copy link
Collaborator

afbjorklund commented May 21, 2019

I saw the same thing with 1.12, --kubernetes-version=v1.12.8

The workaround was --extra-config kubeadm.ignore-preflight-errors=SystemVerification

@tstromberg tstromberg self-assigned this May 21, 2019
@dpandhi-git
Copy link
Contributor

can I work on it ?

@tstromberg
Copy link
Contributor Author

@dpandhi-git - Sorry, didn't see this earlier. I've proposed a PR, do you mind taking a look at it?

Thank you for offering to help!

@dpandhi-git
Copy link
Contributor

@tstromberg : Thanks Thomas for offering to check the issue . I am testing it locally to understand it better. As its closed now, I will look for another issues to contribute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kubernetes-versions Improving support for versions of Kubernetes good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants