--mount-string does not work on hyperkit with non-default profile #12675

Gibstick · 2021-10-07T14:19:21Z

Steps to reproduce the issue:

mkdir -p /tmp/minikube-mount-test
minikube -p mount-test start --driver hyperkit --mount --mount-string /tmp/minikube-mount-test:/test
minikube -p mount-test ssh ls /test

Run minikube logs --file=logs.txt and drag and drop the log file into this issue

Logs for the profile: logs.txt

Full output of failed command if not minikube start:
Output of minikube -p mount-test start ...:

😄  [mount-test] minikube v1.23.2 on Darwin 10.15.7
✨  Using the hyperkit driver based on user configuration
👍  Starting control plane node mount-test in cluster mount-test
🔥  Creating hyperkit VM (CPUs=4, Memory=4000MB, Disk=60000MB) ...
🐳  Preparing Kubernetes v1.22.2 on Docker 20.10.8 ...
    ▪ Generating certificates and keys ...
    ▪ Booting up control plane ...
    ▪ Configuring RBAC rules ...
🔎  Verifying Kubernetes components...
📁  Creating mount /tmp/minikube-mount-test:/test ...
    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🌟  Enabled addons: default-storageclass, storage-provisioner
🏄  Done! kubectl is now configured to use "mount-test" cluster and "default" namespace by default

The mount does not exist, which can be checked by running the last command in the steps: minikube -p mount-test ssh ls /test

ls: cannot access '/test': No such file or directory
ssh: Process exited with status 2

The mountpoint does not exist when the profile is specified in the minikube start command. Here are the cases where it works for me:

Using the default profile, leaving off -p from all of my commands
Workaround: If I explicitly set the profile using minikube config set profile mount-test before I start the VM.
If the VM already exists, I can also use minikube profile mount-test and start the VM again, without needing to stop it first. Using the config setting works as well.

Some other bugs I found that could possibly be related:

The text was updated successfully, but these errors were encountered:

spowelljr · 2021-10-14T18:54:52Z

Just discovered this as well

spowelljr · 2021-10-14T19:24:17Z

Found the root of the issue, we're not passing the profile into the mount command.

https://github.com/kubernetes/minikube/blob/master/pkg/minikube/node/config.go#L68

fernandrone · 2021-11-03T20:16:52Z

I just downloaded https://github.com/kubernetes/minikube/releases/tag/v1.24.0-beta.0 which is supposed to have the fix and I'm experiencing a similar issue. The "test" folder is created on the VM but the folder still doesn't seem to be mounted, because its contents are not there.

mkdir -p /tmp/minikube-mount-test
touch /tmp/minikube-mount-test/hello.txt
minikube -p mount-test start --driver hyperkit --mount --mount-string /tmp/minikube-mount-test:/test
minikube -p mount-test ssh ls /test

ls test will succeed but with no output.

I have no problem with the docker profile FWIW

spowelljr · 2021-11-03T20:34:19Z

Hi @fernandrone, I just tried your exact instructions:

% mkdir -p /tmp/minikube-mount-test           
% touch /tmp/minikube-mount-test/hello.txt
% ./minikube-darwin-amd64 -p mount-test start --driver hyperkit --mount --mount-string /tmp/minikube-mount-test:/test
😄  [mount-test] minikube v1.24.0-beta.0 on Darwin 12.0.1
✨  Using the hyperkit driver based on user configuration
💾  Downloading driver docker-machine-driver-hyperkit:
    > docker-machine-driver-hyper...: 65 B / 65 B [----------] 100.00% ? p/s 0s
    > docker-machine-driver-hyper...: 8.35 MiB / 8.35 MiB [ 100.00% ? p/s 200ms
🔑  The 'hyperkit' driver requires elevated permissions. The following commands will be executed:

    $ sudo chown root:wheel /Users/user/.minikube/bin/docker-machine-driver-hyperkit 
    $ sudo chmod u+s /Users/user/.minikube/bin/docker-machine-driver-hyperkit 


Password: 
💿  Downloading VM boot image ...
    > minikube-v1.24.0.iso.sha256: 65 B / 65 B [-------------] 100.00% ? p/s 0s
    > minikube-v1.24.0.iso: 225.58 MiB / 225.58 MiB  100.00% 68.91 MiB p/s 3.5s
👍  Starting control plane node mount-test in cluster mount-test
💾  Downloading Kubernetes v1.22.2 preload ...
    > preloaded-images-k8s-v13-v1...: 511.69 MiB / 511.69 MiB  100.00% 69.78 Mi
🔥  Creating hyperkit VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
🐳  Preparing Kubernetes v1.22.2 on Docker 20.10.8 ...
    ▪ Generating certificates and keys ...
    ▪ Booting up control plane ...
    ▪ Configuring RBAC rules ...
🔎  Verifying Kubernetes components...
📁  Creating mount /tmp/minikube-mount-test:/test ...
    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🌟  Enabled addons: storage-provisioner, default-storageclass
🏄  Done! kubectl is now configured to use "mount-test" cluster and "default" namespace by default
% ./minikube-darwin-amd64 -p mount-test ssh ls /test                                                                 
hello.txt

fernandrone · 2021-11-03T21:21:29Z

Alright, that's odd! I'm still on Darwin 11.6.1 though, think this could be related?

(kubectl is also outdated but I'm assuming it's not used at all during cluster setup/mount...)

$ minikube -p mount-test start --driver hyperkit --mount --mount-string /tmp/minikube-mount-test:/test
😄  [mount-test] minikube v1.24.0-beta.0 on Darwin 11.6.1
✨  Using the hyperkit driver based on user configuration
👍  Starting control plane node mount-test in cluster mount-test
🔥  Creating hyperkit VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
❗  This VM is having trouble accessing https://k8s.gcr.io
💡  To pull new external images, you may need to configure a proxy: https://minikube.sigs.k8s.io/docs/reference/networking/proxy/
🐳  Preparing Kubernetes v1.22.2 on Docker 20.10.8 ...
    ▪ Generating certificates and keys ...
    ▪ Booting up control plane ...
    ▪ Configuring RBAC rules ...
🔎  Verifying Kubernetes components...
📁  Creating mount /tmp/minikube-mount-test:/test ...
    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🌟  Enabled addons: storage-provisioner, default-storageclass

❗  /usr/local/bin/kubectl is version 1.18.20, which may have incompatibilites with Kubernetes 1.22.2.
    ▪ Want kubectl v1.22.2? Try 'minikube kubectl -- get pods -A'
🏄  Done! kubectl is now configured to use "mount-test" cluster and "default" namespace by default
$ ls /tmp/minikube-mount-test 
hello.txt
$ minikube -p mount-test ssh ls /test

spowelljr · 2021-11-03T22:17:52Z

I don't think using a slightly older version of Darwin is going to be an issue, I was just on 11.6 a couple of weeks ago. And the kubectl being outdated shouldn't make a difference either.

Leaving the cluster running, run minikube -p mount-test mount /tmp/minikube-mount-test:/test2 --alsologtostderr and see if there are any errors in the output.

fernandrone · 2021-11-03T22:42:34Z

Yeah, it fails!

minikube -p mount-test mount /tmp/minikube-mount-test:/test2 --alsologtostderr
I1103 19:39:29.375386   13030 out.go:297] Setting OutFile to fd 1 ...
I1103 19:39:29.375767   13030 out.go:349] isatty.IsTerminal(1) = true
I1103 19:39:29.375777   13030 out.go:310] Setting ErrFile to fd 2...
I1103 19:39:29.375784   13030 out.go:349] isatty.IsTerminal(2) = true
I1103 19:39:29.375879   13030 root.go:313] Updating PATH: /Users/fernandocardoso/.minikube/bin
I1103 19:39:29.376145   13030 mustload.go:65] Loading cluster: mount-test
I1103 19:39:29.376494   13030 config.go:176] Loaded profile config "mount-test": Driver=hyperkit, ContainerRuntime=docker, KubernetesVersion=v1.22.2
I1103 19:39:29.376945   13030 main.go:130] libmachine: Found binary path at /Users/fernandocardoso/.minikube/bin/docker-machine-driver-hyperkit
I1103 19:39:29.377007   13030 main.go:130] libmachine: Launching plugin server for driver hyperkit
I1103 19:39:29.389416   13030 main.go:130] libmachine: Plugin server listening at address 127.0.0.1:51824
I1103 19:39:29.390030   13030 main.go:130] libmachine: () Calling .GetVersion
I1103 19:39:29.390637   13030 main.go:130] libmachine: Using API Version  1
I1103 19:39:29.390657   13030 main.go:130] libmachine: () Calling .SetConfigRaw
I1103 19:39:29.391019   13030 main.go:130] libmachine: () Calling .GetMachineName
I1103 19:39:29.391163   13030 main.go:130] libmachine: (mount-test) Calling .GetState
I1103 19:39:29.391326   13030 main.go:130] libmachine: (mount-test) DBG | exe=/Users/fernandocardoso/.minikube/bin/docker-machine-driver-hyperkit uid=0
I1103 19:39:29.391459   13030 main.go:130] libmachine: (mount-test) DBG | hyperkit pid from json: 12903
I1103 19:39:29.393115   13030 host.go:66] Checking if "mount-test" exists ...
I1103 19:39:29.393562   13030 main.go:130] libmachine: Found binary path at /Users/fernandocardoso/.minikube/bin/docker-machine-driver-hyperkit
I1103 19:39:29.393619   13030 main.go:130] libmachine: Launching plugin server for driver hyperkit
I1103 19:39:29.407415   13030 main.go:130] libmachine: Plugin server listening at address 127.0.0.1:51828
I1103 19:39:29.407949   13030 main.go:130] libmachine: () Calling .GetVersion
I1103 19:39:29.408487   13030 main.go:130] libmachine: Using API Version  1
I1103 19:39:29.408509   13030 main.go:130] libmachine: () Calling .SetConfigRaw
I1103 19:39:29.408857   13030 main.go:130] libmachine: () Calling .GetMachineName
I1103 19:39:29.409021   13030 main.go:130] libmachine: (mount-test) Calling .DriverName
I1103 19:39:29.409184   13030 main.go:130] libmachine: (mount-test) Calling .DriverName
I1103 19:39:29.409835   13030 main.go:130] libmachine: (mount-test) Calling .DriverName
I1103 19:39:29.431603   13030 out.go:176] 📁  Mounting host path /tmp/minikube-mount-test into VM as /test2 ...
📁  Mounting host path /tmp/minikube-mount-test into VM as /test2 ...
I1103 19:39:29.450182   13030 out.go:176]     ▪ Mount type:
    ▪ Mount type:
I1103 19:39:29.468288   13030 out.go:176]     ▪ User ID:      docker
    ▪ User ID:      docker
I1103 19:39:29.488171   13030 out.go:176]     ▪ Group ID:     docker
    ▪ Group ID:     docker
I1103 19:39:29.507677   13030 out.go:176]     ▪ Version:      9p2000.L
    ▪ Version:      9p2000.L
I1103 19:39:29.526334   13030 out.go:176]     ▪ Message Size: 262144
    ▪ Message Size: 262144
I1103 19:39:29.545302   13030 out.go:176]     ▪ Permissions:  755 (-rwxr-xr-x)
    ▪ Permissions:  755 (-rwxr-xr-x)
I1103 19:39:29.563236   13030 out.go:176]     ▪ Options:      map[]
    ▪ Options:      map[]
I1103 19:39:29.581227   13030 out.go:176]     ▪ Bind Address: 192.168.64.1:51832
    ▪ Bind Address: 192.168.64.1:51832
I1103 19:39:29.581569   13030 ssh_runner.go:152] Run: /bin/bash -c "[ "x$(findmnt -T /test2 | grep /test2)" != "x" ] && sudo umount -f /test2 || echo "
I1103 19:39:29.599274   13030 out.go:176] 🚀  Userspace file server:
🚀  Userspace file server: I1103 19:39:29.599314   13030 main.go:130] libmachine: (mount-test) Calling .GetSSHHostname
ufs starting
I1103 19:39:29.599643   13030 main.go:130] libmachine: (mount-test) Calling .GetSSHPort
I1103 19:39:29.599885   13030 main.go:130] libmachine: (mount-test) Calling .GetSSHKeyPath
I1103 19:39:29.600058   13030 main.go:130] libmachine: (mount-test) Calling .GetSSHUsername
I1103 19:39:29.600225   13030 sshutil.go:53] new ssh client: &{IP:192.168.64.26 Port:22 SSHKeyPath:/Users/fernandocardoso/.minikube/machines/mount-test/id_rsa Username:docker}
I1103 19:39:29.648213   13030 mount.go:169] unmount for /test2 ran successfully
I1103 19:39:29.648238   13030 ssh_runner.go:152] Run: /bin/bash -c "sudo mkdir -m 755 -p /test2"
I1103 19:39:29.663071   13030 ssh_runner.go:152] Run: /bin/bash -c "sudo mount -t 9p -o dfltgid=$(grep ^docker: /etc/group | cut -d: -f3),dfltuid=$(id -u docker),msize=262144,port=51832,trans=tcp,version=9p2000.L 192.168.64.1 /test2"
I1103 19:40:01.464842   13030 ssh_runner.go:192] Completed: /bin/bash -c "sudo mount -t 9p -o dfltgid=$(grep ^docker: /etc/group | cut -d: -f3),dfltuid=$(id -u docker),msize=262144,port=51832,trans=tcp,version=9p2000.L 192.168.64.1 /test2": (31.801006272s)
I1103 19:40:01.486160   13030 out.go:176]

W1103 19:40:01.486323   13030 out.go:241] ❌  Exiting due to GUEST_MOUNT_COULD_NOT_CONNECT: /bin/bash -c "sudo mount -t 9p -o dfltgid=$(grep ^docker: /etc/group | cut -d: -f3),dfltuid=$(id -u docker),msize=262144,port=51832,trans=tcp,version=9p2000.L 192.168.64.1 /test2": Process exited with status 32
stdout:

stderr:
mount: /test2: mount(2) system call failed: Connection timed out.

❌  Exiting due to GUEST_MOUNT_COULD_NOT_CONNECT: /bin/bash -c "sudo mount -t 9p -o dfltgid=$(grep ^docker: /etc/group | cut -d: -f3),dfltuid=$(id -u docker),msize=262144,port=51832,trans=tcp,version=9p2000.L 192.168.64.1 /test2": Process exited with status 32
stdout:

stderr:
mount: /test2: mount(2) system call failed: Connection timed out.

W1103 19:40:01.486488   13030 out.go:241] 💡  Suggestion:

    If the host has a firewall:

    1. Allow a port through the firewall
    2. Specify "--port=<port_number>" for "minikube mount"
💡  Suggestion:

    If the host has a firewall:

    1. Allow a port through the firewall
    2. Specify "--port=<port_number>" for "minikube mount"
W1103 19:40:01.486502   13030 out.go:241]

W1103 19:40:01.489144   13030 out.go:241] ╭────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                                                        │
│    😿  If the above advice does not help, please let us know:                                                          │
│    👉  https://github.com/kubernetes/minikube/issues/new/choose                                                        │
│                                                                                                                        │
│    Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.                                 │
│    Please also attach the following file to the GitHub issue:                                                          │
│    - /var/folders/xn/w2x__7cn3p18kyhzb88chvsc0000gp/T/minikube_mount_f9c22db304034f1ce4f2b4a3d3a72c07b537c16e_0.log    │
│                                                                                                                        │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                                                        │
│    😿  If the above advice does not help, please let us know:                                                          │
│    👉  https://github.com/kubernetes/minikube/issues/new/choose                                                        │
│                                                                                                                        │
│    Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.                                 │
│    Please also attach the following file to the GitHub issue:                                                          │
│    - /var/folders/xn/w2x__7cn3p18kyhzb88chvsc0000gp/T/minikube_mount_f9c22db304034f1ce4f2b4a3d3a72c07b537c16e_0.log    │
│                                                                                                                        │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
I1103 19:40:01.508612   13030 out.go:176]

I guess this could be a different issue, possibly #12729

UPDATE: it doesn't work properly on the default profile either, so seems unrelated to this specific bug. I'll keep keep investigating and if needed I'll add more information to the issue above. Thanks @spowelljr 👍🏻

abhishekbhutra · 2021-12-20T20:43:19Z

Failing on macos caalina too

Joxtacy · 2022-06-17T13:54:44Z

I am facing the same issues on Monterey (v12.4) as well. Intel chip.

➜  ~ minikube mount /Users/joxtacy/Projects/integration-hub:/test2 --alsologtostderr
I0617 22:49:32.192246   92558 out.go:297] Setting OutFile to fd 1 ...
I0617 22:49:32.192755   92558 out.go:349] isatty.IsTerminal(1) = true
I0617 22:49:32.192773   92558 out.go:310] Setting ErrFile to fd 2...
I0617 22:49:32.192787   92558 out.go:349] isatty.IsTerminal(2) = true
I0617 22:49:32.192912   92558 root.go:315] Updating PATH: /Users/joxtacy/.minikube/bin
I0617 22:49:32.193162   92558 mustload.go:65] Loading cluster: minikube
I0617 22:49:32.193512   92558 config.go:176] Loaded profile config "minikube": Driver=hyperkit, ContainerRuntime=docker, KubernetesVersion=v1.23.3
I0617 22:49:32.193948   92558 main.go:130] libmachine: Found binary path at /Users/joxtacy/.minikube/bin/docker-machine-driver-hyperkit
I0617 22:49:32.194020   92558 main.go:130] libmachine: Launching plugin server for driver hyperkit
I0617 22:49:32.205431   92558 main.go:130] libmachine: Plugin server listening at address 127.0.0.1:61946
I0617 22:49:32.206264   92558 main.go:130] libmachine: () Calling .GetVersion
I0617 22:49:32.206885   92558 main.go:130] libmachine: Using API Version  1
I0617 22:49:32.206925   92558 main.go:130] libmachine: () Calling .SetConfigRaw
I0617 22:49:32.207337   92558 main.go:130] libmachine: () Calling .GetMachineName
I0617 22:49:32.207548   92558 main.go:130] libmachine: (minikube) Calling .GetState
I0617 22:49:32.207719   92558 main.go:130] libmachine: (minikube) DBG | exe=/Users/joxtacy/.minikube/bin/docker-machine-driver-hyperkit uid=0
I0617 22:49:32.207835   92558 main.go:130] libmachine: (minikube) DBG | hyperkit pid from json: 91843
I0617 22:49:32.209496   92558 host.go:66] Checking if "minikube" exists ...
I0617 22:49:32.209930   92558 main.go:130] libmachine: Found binary path at /Users/joxtacy/.minikube/bin/docker-machine-driver-hyperkit
I0617 22:49:32.210005   92558 main.go:130] libmachine: Launching plugin server for driver hyperkit
I0617 22:49:32.220894   92558 main.go:130] libmachine: Plugin server listening at address 127.0.0.1:61948
I0617 22:49:32.221465   92558 main.go:130] libmachine: () Calling .GetVersion
I0617 22:49:32.221923   92558 main.go:130] libmachine: Using API Version  1
I0617 22:49:32.221962   92558 main.go:130] libmachine: () Calling .SetConfigRaw
I0617 22:49:32.222258   92558 main.go:130] libmachine: () Calling .GetMachineName
I0617 22:49:32.222423   92558 main.go:130] libmachine: (minikube) Calling .DriverName
I0617 22:49:32.222614   92558 main.go:130] libmachine: (minikube) Calling .DriverName
I0617 22:49:32.224402   92558 main.go:130] libmachine: (minikube) Calling .DriverName
I0617 22:49:32.254969   92558 out.go:176] 📁  Mounting host path /Users/joxtacy/Projects/integration-hub into VM as /test2 ...
📁  Mounting host path /Users/joxtacy/Projects/integration-hub into VM as /test2 ...
I0617 22:49:32.276917   92558 out.go:176]     ▪ Mount type:
    ▪ Mount type:
I0617 22:49:32.286773   92558 out.go:176]     ▪ User ID:      docker
    ▪ User ID:      docker
I0617 22:49:32.312064   92558 out.go:176]     ▪ Group ID:     docker
    ▪ Group ID:     docker
I0617 22:49:32.332946   92558 out.go:176]     ▪ Version:      9p2000.L
    ▪ Version:      9p2000.L
I0617 22:49:32.353814   92558 out.go:176]     ▪ Message Size: 262144
    ▪ Message Size: 262144
I0617 22:49:32.374858   92558 out.go:176]     ▪ Options:      map[]
    ▪ Options:      map[]
I0617 22:49:32.394858   92558 out.go:176]     ▪ Bind Address: 192.168.64.1:61950
    ▪ Bind Address: 192.168.64.1:61950
I0617 22:49:32.395685   92558 ssh_runner.go:195] Run: /bin/bash -c "[ "x$(findmnt -T /test2 | grep /test2)" != "x" ] && sudo umount -f /test2 || echo "
I0617 22:49:32.414898   92558 out.go:176] 🚀  Userspace file server:
🚀  Userspace file server: I0617 22:49:32.414943   92558 main.go:130] libmachine: (minikube) Calling .GetSSHHostname
ufs starting
I0617 22:49:32.415179   92558 main.go:116] stdlog: ufs.go:27 listen tcp 192.168.64.1:61950: bind: can't assign requested address
I0617 22:49:32.415195   92558 main.go:130] libmachine: (minikube) Calling .GetSSHPort
I0617 22:49:32.415457   92558 main.go:130] libmachine: (minikube) Calling .GetSSHKeyPath
I0617 22:49:32.435902   92558 out.go:176] 🛑  Userspace file server is shutdown
🛑  Userspace file server is shutdown
I0617 22:49:32.436216   92558 main.go:130] libmachine: (minikube) Calling .GetSSHUsername
I0617 22:49:32.436856   92558 sshutil.go:53] new ssh client: &{IP:192.168.106.5 Port:22 SSHKeyPath:/Users/joxtacy/.minikube/machines/minikube/id_rsa Username:docker}
I0617 22:49:32.486982   92558 mount.go:168] unmount for /test2 ran successfully
I0617 22:49:32.487042   92558 ssh_runner.go:195] Run: /bin/bash -c "sudo mkdir -p /test2"
I0617 22:49:32.495988   92558 ssh_runner.go:195] Run: /bin/bash -c "sudo mount -t 9p -o dfltgid=$(grep ^docker: /etc/group | cut -d: -f3),dfltuid=$(id -u docker),msize=262144,port=61950,trans=tcp,version=9p2000.L 192.168.64.1 /test2"
I0617 22:50:04.428450   92558 ssh_runner.go:235] Completed: /bin/bash -c "sudo mount -t 9p -o dfltgid=$(grep ^docker: /etc/group | cut -d: -f3),dfltuid=$(id -u docker),msize=262144,port=61950,trans=tcp,version=9p2000.L 192.168.64.1 /test2": (31.931436737s)
I0617 22:50:04.450647   92558 out.go:176]

W0617 22:50:04.450911   92558 out.go:241] ❌  Exiting due to GUEST_MOUNT_COULD_NOT_CONNECT: /bin/bash -c "sudo mount -t 9p -o dfltgid=$(grep ^docker: /etc/group | cut -d: -f3),dfltuid=$(id -u docker),msize=262144,port=61950,trans=tcp,version=9p2000.L 192.168.64.1 /test2": Process exited with status 32
stdout:

stderr:
mount: /test2: mount(2) system call failed: Connection timed out.

❌  Exiting due to GUEST_MOUNT_COULD_NOT_CONNECT: /bin/bash -c "sudo mount -t 9p -o dfltgid=$(grep ^docker: /etc/group | cut -d: -f3),dfltuid=$(id -u docker),msize=262144,port=61950,trans=tcp,version=9p2000.L 192.168.64.1 /test2": Process exited with status 32
stdout:

stderr:
mount: /test2: mount(2) system call failed: Connection timed out.

W0617 22:50:04.451091   92558 out.go:241] 💡  Suggestion:

    If the host has a firewall:

    1. Allow a port through the firewall
    2. Specify "--port=<port_number>" for "minikube mount"
💡  Suggestion:

    If the host has a firewall:

    1. Allow a port through the firewall
    2. Specify "--port=<port_number>" for "minikube mount"
W0617 22:50:04.451137   92558 out.go:241]

W0617 22:50:04.454330   92558 out.go:241] ╭────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                                                        │
│    😿  If the above advice does not help, please let us know:                                                          │
│    👉  https://github.com/kubernetes/minikube/issues/new/choose                                                        │
│                                                                                                                        │
│    Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.                                 │
│    Please also attach the following file to the GitHub issue:                                                          │
│    - /var/folders/8b/r3bv0s1s4j3f36nfr9t6y3k00000gq/T/minikube_mount_8d84d0b405b1c27f30800c954ca2f7053fae6f65_0.log    │
│                                                                                                                        │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                                                        │
│    😿  If the above advice does not help, please let us know:                                                          │
│    👉  https://github.com/kubernetes/minikube/issues/new/choose                                                        │
│                                                                                                                        │
│    Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue.                                 │
│    Please also attach the following file to the GitHub issue:                                                          │
│    - /var/folders/8b/r3bv0s1s4j3f36nfr9t6y3k00000gq/T/minikube_mount_8d84d0b405b1c27f30800c954ca2f7053fae6f65_0.log    │
│                                                                                                                        │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
I0617 22:50:04.475228   92558 out.go:176]

sourabhyadavgit · 2023-01-11T20:07:56Z

hi Guys,

i'm also facing the same issue, any workaround on this?
i'm running minikube on ubuntu (which is again on my windows 11 machine).

spowelljr self-assigned this Oct 14, 2021

spowelljr added area/mount kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Oct 14, 2021

spowelljr added this to the 1.24.0 milestone Oct 14, 2021

spowelljr mentioned this issue Oct 14, 2021

Fix mounting on non-default profile #12711

Merged

spowelljr closed this as completed in #12711 Oct 15, 2021

fernandrone mentioned this issue Nov 4, 2021

minikube mount fails on MacOS Big Sur #12729

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

--mount-string does not work on hyperkit with non-default profile #12675

--mount-string does not work on hyperkit with non-default profile #12675

Gibstick commented Oct 7, 2021

spowelljr commented Oct 14, 2021 •

edited

Loading

spowelljr commented Oct 14, 2021

fernandrone commented Nov 3, 2021

spowelljr commented Nov 3, 2021

fernandrone commented Nov 3, 2021

spowelljr commented Nov 3, 2021

fernandrone commented Nov 3, 2021 •

edited

Loading

abhishekbhutra commented Dec 20, 2021

Joxtacy commented Jun 17, 2022

sourabhyadavgit commented Jan 11, 2023

--mount-string does not work on hyperkit with non-default profile #12675

--mount-string does not work on hyperkit with non-default profile #12675

Comments

Gibstick commented Oct 7, 2021

spowelljr commented Oct 14, 2021 • edited Loading

spowelljr commented Oct 14, 2021

fernandrone commented Nov 3, 2021

spowelljr commented Nov 3, 2021

fernandrone commented Nov 3, 2021

spowelljr commented Nov 3, 2021

fernandrone commented Nov 3, 2021 • edited Loading

abhishekbhutra commented Dec 20, 2021

Joxtacy commented Jun 17, 2022

sourabhyadavgit commented Jan 11, 2023

spowelljr commented Oct 14, 2021 •

edited

Loading

fernandrone commented Nov 3, 2021 •

edited

Loading