-
Notifications
You must be signed in to change notification settings - Fork 558
Kubernetes CoreOS failed to start kubelet #1957
Comments
UPD1: I've removed the plugins volume line from the kubelet.service and it works. On agent node docker daemon doesn't start((( UPD3: Copied the content of the exec_start.conf from master node and it fixed the error. |
@jackfrancis does our acs-engine support coreos too? I have checked, |
@andyzhangx It was supported before #1909 :)
to
and pass it to kubelet as parameter:
instead of using the default? |
@mwieczorek Thanks for the suggestion. Sounds like there is a trade-off if we also want to support coreos, we need to use |
I would like to change the default flexvolume plugin dir in Linux to |
I will try and look into this soon, I integrated CoreOS a while back but think it needs updates after Azure CNI was introduced. You can put stuff in /opt, which is what the CoreOS implementation does (puts kubelet in /opt) — I believe unless it was changed recently. |
@richardjortega, I made a PR#1991 to set flexvolume plugin dir as |
@andyzhangx I wrote those CoreOS examples. I haven’t tried them in about a month or two so things could’ve changed that sideaffected it. |
@andyzhangx If you get 'docker daemon' is not supported on Linux. Please run 'dockerd' directly on the agent nodes, just copy exec_start.conf from master. |
I tried to deploy with kubespray coreos and noticed my kubelet_flexvolumes_plugins_dir: /var/lib/kubelet/volumeplugins variable was not picked up during deployment. In every deployed host, I had to edit /etc/kubernetes/kubelet.env
after that run systemctl restart kubelet Working now |
Is this a request for help?:
YES
Is this an ISSUE or FEATURE REQUEST? (choose one):
ISSUE
What version of acs-engine?:
0.11.0
Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes 1.8.4
What happened:
Unable to connect to the kubernetes cluster with CoreOS as a distro after deployment. Kubelet can't be started because of the file system permission issue:
Dec 20 14:32:24 k8s-master-XXXXXX-0 docker[2794]: /run/torcx/bin/docker: Error response from daemon: error while creating mount source path '/usr/libexec/kubernetes/kubelet-plugins': mkdir /usr/libexec/kubernetes: read-only file system.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
{ "apiVersion": "vlabs", "properties": { "orchestratorProfile": { "orchestratorType": "Kubernetes", "orchestratorVersion": "1.8.4", "kubernetesConfig": { "networkPolicy": "azure", "enableRbac": true } }, "masterProfile": { "count": 1, "dnsPrefix": "yourdnsprefix", "vmSize": "Standard_D2_v2", "storageProfile" : "ManagedDisks", "distro": "coreos" }, "agentPoolProfiles": [ { "name": "agentpool1", "count": 3, "vmSize": "Standard_DS2_v2", "availabilityProfile": "AvailabilitySet", "storageProfile" : "ManagedDisks", "distro": "coreos" } ], "linuxProfile": { "adminUsername": "admin", "ssh": { "publicKeys": [ { "keyData": "" } ] } }, "servicePrincipalProfile": { "clientId": "", "secret": "" } } }
Anything else we need to know:
Tried several times
The text was updated successfully, but these errors were encountered: