Closed seerocode closed 3 years ago
Seems different from #10243
You will need to use a VM driver, until Docker works on M1
Seems different from #10243
You will need to use a VM driver, until Docker works on M1
Okay. So even with the Docker tech preview working?
Seems like it got a timeout, from docker run
. So more network issues, than regular segmentation fault.
But it doesn't seem that it is working, no. It might be possible to troubleshoot more, but not really ready ?
Forgot that we don't have the ISO ready for ARM just yet. So you will just have to wait, I guess
@afbjorklund is there a timeline by any chance I can watch out for?
@seerocode could you please try the following:
minikube delete --all --purge
docker ps | grep minikube
@afbjorklund is there a timeline by any chance I can watch out for?
I can't answer for when Docker Desktop is going out of tech preview, and don't really know the root cause in this issue.
But if you are interested in another VM solution (than Docker's), you can track the ISO development here: #9228
@ilya-zuyev I get no output for docker grep on minikube after trying those steps.
@afbjorklund I'll just wait on new development for now. I am wondering though if the last error is something to worry about:
Unable to find image 'gcr.io/k8s-minikube/kicbase:v0.0.17@sha256:1cd2e039ec9d418e6380b2fa0280503a72e5b282adea674ee67882f59f4f546e' locally
docker: Error response from daemon: Get https://gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
I am unable to ping https://gcr.io/v2/. My firewall is not on.
Hmm, NVM. I tried docker pull docker.pkg.github.com/kubernetes/minikube/kicbase:v0.0.17
and still having an issue there.
One thing I can't tell from here is if the arm64 binary of minikube was downloaded, or the amd64.
At least previously, we failed in mysterious ways if the amd64 version of minikube was executed on arm64.
I can confirm that this works for me on an M1 mac:
curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-darwin-arm64
sudo install minikube-darwin-amd64 /usr/local/bin/minikube
@tstromberg I uninstalled minikube and tried this install but still no dice with Docker as a driver. Does this fully work for you with Docker?
curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-darwin-arm64 sudo install minikube-darwin-amd64 /usr/local/bin/minikube
Should have been "arm64", but is being fixed in PR #10337
Thanks @afbjorklund! I installed again after PR was merged and still getting this error:
...
โ Exiting due to GUEST_PROVISION: Failed to start host: recreate: creating host: create: creating: setting up container node: preparing volume for minikube container: docker run --rm --entrypoint /usr/bin/test -v minikube:/var gcr.io/k8s-minikube/kicbase:v0.0.17@sha256:1cd2e039ec9d418e6380b2fa0280503a72e5b282adea674ee67882f59f4f546e -d /var/lib: exit status 125
stdout:
stderr:
Unable to find image 'gcr.io/k8s-minikube/kicbase:v0.0.17@sha256:1cd2e039ec9d418e6380b2fa0280503a72e5b282adea674ee67882f59f4f546e' locally
docker: Error response from daemon: Get https://gcr.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See 'docker run --help'.
I am not using a proxy or VPN as indicated in the documentation: https://minikube.sigs.k8s.io/docs/handbook/vpn_and_proxy/
Additionally, these are the listed known issues for the Docker M1 tech preview that may be relevant:
- The DNS name host.docker.internal only works if you add --add-host=host.docker.internal:host-gateway to the docker run command
- The DNS name vm.docker.internal does not work.
- Kubernetes does not initialize because of a missing DNS name.
I see this command in the logs: docker run --rm --entrypoint /usr/bin/test -v minikube:/var gcr.io/k8s-minikube/kicbase:v0.0.17@sha256:1cd2e039ec9d418e6380b2fa0280503a72e5b282adea674ee67882f59f4f546e -d /var/lib
Installed minikube with these commands
curl -LO https://storage.googleapis.com/minikube/releases/latest/minikube-darwin-arm64 sudo install minikube-darwin-arm64 /usr/local/bin/minikube
But it doesn't work, got the error:
minikube start
๐ minikube v1.17.1 on Darwin 11.2 (arm64)
โจ Using the docker driver based on existing profile
๐ Starting control plane node minikube in cluster minikube
๐ Pulling base image ...
๐ Updating the running docker "minikube" container ...
๐ณ Preparing Kubernetes v1.20.2 on Docker 20.10.2 ...- E0207 18:03:30.747601 15185 start.go:99] Unable to get host IP: resolve dns to ip: docker exec -t minikube dig +short host.docker.internal: exit status 9
stdout:
;; connection timed out; no servers could be reached
stderr:
โ Exiting due to GUEST_START: Failed to setup kubeconfig: resolve dns to ip: docker exec -t minikube dig +short host.docker.internal: exit status 9 stdout: ;; connection timed out; no servers could be reached
stderr:
๐ฟ If the above advice does not help, please let us know: ๐ https://github.com/kubernetes/minikube/issues/new/choose
Issue resolved with the new Docker release! https://www.docker.com/blog/new-docker-desktop-preview-for-apple-m1-released/
Installations from homebrew did not work. installing Docker client comes along with kubernetes which fixed the issue
https://hub.docker.com/search?q=&type=edition&offering=community
Confirming this all worked fine for me. Downloaded the M1 .dmg from docker's website and brew install minikube
and could access minikube dashboard
w/o any issues.
I have the error: โ Exiting due to DRV_UNSUPPORTED_OS: The driver 'parallels' is not supported on darwin/arm64
After trying to start Minikube on parallels
Exiting due to GUEST_PROVISION_CONTAINER_EXITED: Docker container exited prematurely after it was created, consider investigating Docker's performance/health.
amd64
sudo install minikube-darwin-arm64 /usr/local/bin/minikube
hi everyone, I also faced issue with latest version of minikube (v1.33.0) on my MacBook Pro M1 (2020) running Docker Desktop and macOS Sonomo 14.5
minikube start
downloaded images and after showing Creating docker container (CPUs=2, Memory=2200MB) ...
for few minutes, next line gave error like Exiting due to DRV_CREATE_TIMEOUT: Failed to start host: recreate: creating host: create host timed out in 360.000000 seconds
minikube v1.33.1 on Darwin 14.4.1 (arm64)
Automatically selected the docker driver
Using Docker Desktop driver with root privileges
Starting "minikube" primary control-plane node in "minikube" cluster
Pulling base image v0.0.44 ...
Downloading Kubernetes v1.30.0 preload ...
> preloaded-images-k8s-v18-v1...: 319.81 MiB / 319.81 MiB 100.00% 14.08 M
> gcr.io/k8s-minikube/kicbase...: 381.76 MiB / 435.76 MiB 87.61% 12.82 Mi
Creating docker container (CPUs=2, Memory=2200MB) ...-
StartHost failed, but will try again: creating host: create host timed out in 360.000000 seconds
docker "minikube" container is missing, will recreate.
Creating docker container (CPUs=2, Memory=2200MB) ...\
StartHost failed, but will try again: creating host: create host timed out in 360.000000 seconds
Failed to start docker container. Running "minikube delete" may fix it: recreate: creating host: create host timed out in 360.000000 seconds
Exiting due to DRV_CREATE_TIMEOUT: Failed to start host: recreate: creating host: create host timed out in 360.000000 seconds
Suggestion: Try 'minikube delete', and disable any conflicting VPN or firewall software
Related issue: https://github.com/kubernetes/minikube/issues/7072
I spent hours on Github issue (7072) as well others to find a solution, but all were pointing to either changing driver or older issues when Docker wasn't supported for M1 natively.
While checking minikube logs
, I found docker run command to extract downloaded tar file in image. I thought of running that manually myself and then Docker gave proper error message.
All I need to do was adding /Users/kirtimaan/.minikube
folder to Docker's preferences -> Resources -> File Sharing -> Virtual file shares.
Once added, then Docker has allowed reading/mounting files stored in this page, and simply minikube delete
and minikube start
works like charm.
This Docker resource path addition is missing in documentation and tutorials, and thus could be a challenge for starters like me, who are using Docker driver with minikube.
Thought of sharing it here, so anyone else facing similar issue on M1 MacBook can save time.
Steps to reproduce the issue:
bridge100
inet 192.168.64.1minikube start --driver=docker --alsologtostderr -v=5
Full output of failed command:
Optional: Full output of
minikube logs
command: