search

kubernetes-retired / kubeadm-dind-cluster

[EOL] A Kubernetes multi-node test cluster based on kubeadm
Apache License 2.0
1.11k stars 274 forks source link

dind-cluster-v1.13.sh and dind-cluster-v1.10.sh up failed on windows 10 #276

Closed nasseur closed 5 years ago

nasseur commented 5 years ago

I'm trying to use the kubeadm-dind-cluster on Windows 10 but i'm not able to start it. I'm getting the below error when launching the command: ./dind-cluster-v1.13.sh up

Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"C:/Program Files/Git/usr/bin/ba sh\": stat C:/Program Files/Git/usr/bin/bash: no such file or directory": unknown. ./dind-cluster-v1.13.sh: line 790: KUBECTL_LINUX_SHA1: unbound variable

jamesmstone commented 5 years ago

I'm getting the same issue... But using Alpine Linux.

$ ./dind-cluster-v1.13.sh up
WARNING: No swap limit support
WARNING: No swap limit support
WARNING: No swap limit support
WARNING: No swap limit support
* Making sure DIND image is up to date 
sha256:0fcb655948a1fa20f5a2100983755edc8f0d763248bda217b3454d82d5cd3be4: Pulling from mirantis/kubeadm-dind-cluster
Digest: sha256:0fcb655948a1fa20f5a2100983755edc8f0d763248bda217b3454d82d5cd3be4
Status: Image is up to date for mirantis/kubeadm-dind-cluster@sha256:0fcb655948a1fa20f5a2100983755edc8f0d763248bda217b3454d82d5cd3be4
docker: Error response from daemon: failed to create endpoint modest_kepler on network bridge: failed to add the host (vethb616424) <=> sandbox (veth601a2fb) pair interfaces: operation not supported.
ERRO[0000] error waiting for container: context canceled 
./dind-cluster-v1.13.sh: line 789: KUBECTL_LINUX_SHA1: unbound variable
nasseur commented 5 years ago

@jamesmstone , I have got also this error on linux but i resolved it by installing kubeadm and kubelet.

SteveParson commented 5 years ago

I have a related issue. I believe that the parser for the image name needs to be reworked. 

WARNING: No memory limit support
WARNING: No swap limit support
WARNING: No memory limit support
WARNING: No swap limit support
WARNING: No memory limit support
WARNING: No swap limit support
WARNING: No memory limit support
WARNING: No swap limit support
* Making sure DIND image is up to date
FATA[0000] Invalid repository name (kubeadm-dind-cluster:596f7d093470c1dc3a3e4466bcdfb34438a99b90-v1.13), only [a-z0-9-_.] are allowed

Examining further, it turns out that the env variable DIND_IMAGE becomes mirantis/kubeadm-dind-cluster:596f7d093470c1dc3a3e4466bcdfb34438a99b90-v1.13@sha256:0fcb655948a1fa20f5a2100983755edc8f0d763248bda217b3454d82d5cd3be4

As a quick workaround, you can change the lines around 2286 to the following

if [[ ! ( ${DIND_IMAGE} =~ local ) && ! ${DIND_SKIP_PULL:-} ]]; then
  dind::step "Making sure DIND image is up to date"
  DIND_IMAGE=`echo ${DIND_IMAGE} | cut -f1 -d"@"`
  docker pull "${DIND_IMAGE}" >&2
fi
fejta-bot commented 5 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale

fejta-bot commented 5 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten

fejta-bot commented 5 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close

k8s-ci-robot commented 5 years ago

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/kubeadm-dind-cluster/issues/276#issuecomment-506447327): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >Send feedback to sig-testing, kubernetes/test-infra and/or [fejta](https://github.com/fejta). >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.