kubernetes-vagrant-centos-cluster: vagrant up failed while configuring node3 with Win10

Environment

OS:WIN10
kubernetes:1.11.0
vagrant: 2.1.5
virtualbox:5.2.18

What I did?

after " vagrant up" got messages:

 node3: configure node3
 node3: Failed to start kubelet.service: Unit is not loaded properly: Bad message.
 node3: See system logs and 'systemctl status kubelet.service' for details.
 node3: Failed to execute operation: Bad message
 node3: Failed to start kube-proxy.service: Unit is not loaded properly: Bad message.
 node3: See system logs and 'systemctl status kube-proxy.service' for details.
 node3: Failed to execute operation: Bad message
 node3: deploy coredns
 node3: /tmp/vagrant-shell: ./dns-deploy.sh: /bin/bash^M: bad interpreter: No such file or directory

the Solution for Win10 got messages:

unable to recognize "STDIN": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: connect: connection refused
unable to recognize "STDIN": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: connect: connection refused
unable to recognize "STDIN": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: connect: connection refused
unable to recognize "STDIN": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: connect: connection refused
unable to recognize "STDIN": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: connect: connection refused
unable to recognize "STDIN": Get https://172.17.8.101:6443/api?timeout=32s: dial tcp 172.17.8.101:6443: connect: connection refused

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 17 (8 by maintainers)

Most upvoted comments

In a word ,to make this project run on my PC(OS:Windows 10 Enterprise) , I modify all the files in \kubernetes-vagrant-centos-cluster\systemd as following:

[Unit]
Description=Kubernetes Kube-Proxy Server
Documentation=https://github.com/GoogleCloudPlatform/kubernetes
After=network.target
[Service]
EnvironmentFile=-/etc/kubernetes/config
EnvironmentFile=-/etc/kubernetes/proxy
ExecStart=/usr/bin/kube-proxy $KUBE_LOGTOSTDERR $KUBE_LOG_LEVEL $KUBE_MASTER $KUBE_PROXY_ARGS
Restart=on-failure
LimitNOFILE=65536
[Install]
WantedBy=multi-user.target

Attention:ExecStart is in one line.

zhaoenweiex on Oct 19, 2018