minikube mount fails on MacOS Big Sur #12729
Labels
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
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 |
medyagh
added
help wanted
|
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:/testI mounted a volume Also interestingly, every minikube mount /tmp/test2:/test2 --v=7 --alsologtostderrThe 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 }') |
spowelljr
added
priority/important-longterm
|
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 |
k8s-ci-robot
added
the
lifecycle/stale
|
/remove-lifecycle stale |
k8s-ci-robot
removed
the
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 |
k8s-ci-robot
added
the
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 |
k8s-ci-robot
added
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 was referenced Jan 27, 2023
|
this issue must be fixed by this PR #15720 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce the issue:
brew install hyperkit && brew install minikubeminikube startminikube mount /folder:/folderRun
minikube logs --file=logs.txtand 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: