-
Notifications
You must be signed in to change notification settings - Fork 558
Windows failed to create kubelet: failed to get docker version #4118
Comments
Today I created a new k8s cluster due to the old one crashed #4046, but the Windows nodes didn't appear in "kubectl get nodes", although the Windows VMs were created in Azure. Do we have workaround? It is a blocking issue, because we are unable to run any workloads in k8s now. Thanks |
The PR linked above fixes it. Hoping to get that merged soon. As a stop gap, if you remote into each machine and set the docker version manually to 17.06.2-ee-16: #3852 (comment) |
@PatrickLang @jsturtevant The latest kubelet.err.log: Thanks |
Seems this PR is not included in 0.24.2? |
I don't beleive it is, as 0.24.2 was a patch release. The change is in master so next release should be avaliable or you can build from master. |
As a temporary workaround, you can also deploy the previous Windows image by setting
|
The workaround works, Thanks |
Should pinning the image be the norm, not just a workaround? This issue would also have happened on scale operations on working clusters, right? |
The scale does not work also. I met this issue first when scaling my cluster. |
Docker version is pinned now in 0.24.3, but you can set it it the API model if you want a different version. |
Is this a request for help?:
no
Is this an ISSUE or FEATURE REQUEST? (choose one):
issue
What version of acs-engine?:
any using windows server 1803 image
Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes
What happened:
deployed 1803 windows container images. Windows nodes never join cluster. get the error as described here: kubernetes/kubernetes#69996
What you expected to happen:
Kubelet to start and and connect nodes to the cluster
How to reproduce it (as minimally and precisely as possible):
deploy a k8s cluster with 1803 node as of today
Anything else we need to know:
Because the Docker version is installed by the image the version got auto upgraded. Should pin the Docker version to a known working value so that Windows Server moving to new Docker version upgrades in Azure don't cause deployment errors.
The text was updated successfully, but these errors were encountered: