Closed jmholla closed 3 years ago
Whelp, there's no ability to attach files, so here is the output of --alsologtostderr
:
This does work if you call minikube delete
. It is not apparent why when reconstructing the container without this that it does not want to mount the paths at the right time.
@jmholla If you want to delete your existing minikube instance minikube delete
is the recommended way.
Does using minikube delete
resolve your issue?
minikube delete
did work. What about the way the container is being run causes mounting without minikube delete to happen so late in the process?
@jmholla Docker driver does not support changing mount options. Removing underlying container using docker rm
doesn't help here.
The issue here is that minikube still thinks it has an active container since you pulled the rug out from underneath minikube by deleting it directly via docker. The error message you're seeing would be the same if you tried to change mount options on a second minikube start without having stopped or deleted anything. minikube stop
then docker rm minikube
is never a recommended flow.
I'm going to go ahead and close this issue for now. If you have any questions, please feel free to reopen this issue.
Steps to reproduce the issue:
minikube stop
docker rm minikube
minikube start --mount --mount-string="$HOME:/src" --driver=docker
I would expect the mount to happen during container creation.
This is on Linux Mint.
Full output of failed command:
(I'll attempt to attach the output with
--alsologtostderr
as a file because it keeps repeatedly spitting out the same complaint about the container not existing which will just fill up this issue.)Full output of
minikube start
command used, if not already included:See above
Optional: Full output of
minikube logs
command: