-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to start docker container: docker copy to minikube:/home/docker/.ssh/authorized_keys, output: lstat tmpf-memory-asset: no such file or directory #9869
Comments
Interesting - I have not seen this before. Could you include the output of:
|
Hello Thomas, thank you for responding to my request. Below is the output of the command you suggested `sudo minikube start --alsologtostderr -v=1 W1212 14:09:45.560009 15696 out.go:146] ❌ Exiting due to DRV_AS_ROOT: The "docker" driver should not be used with root privileges. ` |
@tstromberg I have the same issue, when I run
|
@esentai8 I wonder if you have installed minikube using snap ? do u mind trying this URL to see if this fixes your problem too ? https://storage.googleapis.com/minikube/latest/minikube-linux-amd64 |
@esentai8 I belive we have fixed this on the HEAd and it will be included on minikube 1.17.0 |
Cool, thank you! I will try one more time today using 1.17 and will write my feedback here |
Had the same log output; the issue was caused by Docker for me. Purging and reinstalling docker through |
@esentai8 Did upgrading to latest minikube (v1.17.1) help here? |
On Arch.
Docker service is up and running. Is this relative to the issue? |
@horseinthesky based on your output I'd check whether minikube network is created among docker networks ( |
@LordBertson While it is trying to create a cluster I see the minikube network in the list
iptables looks like this
Everything seems fine. After minikube fails to create a cluster the network and the container are deleted. |
@horseinthesky in that case I'd try the default: I'd definitely consider uninstalling Minikube and installing from scratch, here I'd go for official binaries (described here). If that does not help and your current set up allows it, I would consider reinstalling docker from scratch, as described in their official docs, but since Arch is not covered you can also just use it as a reference material and find respective packages in your preferred package manager I suppose. |
@LordBertson I've tried all these steps but this doesn't help. I've opened #10496 since it seems different issue. |
@esentai8 did you have a chance to try minikube 1.17.1 or 1.18.0? Can we close this issue? |
Yes, issue is resolved. Thank you! |
Excellent, I'll go ahead and close this issue then. |
I am using Ubuntu 20.04 LTS
Steps to reproduce the issue:
1.Installed kubectl according to the instructions from the official website
2. Installed minicube according to the instructions from the official website
3. running 'minikube start'
Full output of failed command:
Full output of
minikube start
command used, if not already included:Optional: Full output of
minikube logs
command:I tried many possible solutions available on the internet (e.g. deleting minikube and restarting, destroying all docker servers running and restarting etc.)
The text was updated successfully, but these errors were encountered: