-
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
minikube mount fails on MacOS Big Sur #12729
Comments
Thank you @evilhamsterman for creating this issue, I agree with you this seems to be a bug that we should fix in the minikube code. do u verify that work arround works for you too ? I am curious what makes your Mac OS different than others, that would require this work arround ? I accept any PR that would fix this for everyone |
CC: @spowelljr who recently touched the mount code and have more context than me |
The workaround does work if I find the cluster ip range with |
Just reporting that I have the same issue on MacOS Monterey with the beta release of minikube Logs of minikube start --alsologtostderr --driver hyperkit --mount --mount-string /tmp/minikube-mount-test:/test
I mounted a volume Also interestingly, every minikube mount /tmp/test2:/test2 --v=7 --alsologtostderr
The one below, using minikube mount /tmp/test2:/test2 --v=7 --alsologtostderr --ip $(minikube ip)
minikube mount /tmp/test2:/test2 --v=7 --alsologtostderr --ip $(ifconfig en0 | grep "inet\b" | awk '{ print $2 }')
|
Hi @fernandrone, the reason the mount on start didn't output any errors is because errors are suppressed for mount on start unless |
@spowelljr does it work for you if try also changing the IP as mentioned by @evilhamsterman in their comment? With |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
this issue must be fixed by this PR #15720 |
Steps to reproduce the issue:
brew install hyperkit && brew install minikube
minikube start
minikube mount /folder:/folder
Run
minikube logs --file=logs.txt
and drag and drop the log file into this issueFull output of failed command if not
minikube start
:logs.txt
minikube_mount_90d1df7cf73d2307a9c342b14ba42d70e548606c_0.log
This appears to be the same issue in #12537 and #11475. I'm not sure why the reporters closed those tickets when they found a workaround because this appears to still be an issue in the code. A workaround should not be required
The text was updated successfully, but these errors were encountered: