Minikube mount issue: Status 32, connection refused

StefanOid commented 5 months ago

What Happened?

Trying to use minikube mount /home/stefan/Documents/data/:tmp/data/ --ip=192.168.49.2 (result of minikube ip) --port=32681 (used sudo ufw allow 32681/tcp beforehand)

Result:

📁 Mounting host path /home/stefan/Documents/data into VM as /tmp/data/ ... ▪ Mount type: 9p ▪ User ID: docker ▪ Group ID: docker ▪ Version: 9p2000.L ▪ Message Size: 262144 ▪ Options: map[] ▪ Bind Address: 192.168.49.2:36801 🚀 Userspace file server: ufs starting 🛑 Userspace file server is shutdown

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

stderr: mount: /tmp/data: mount(2) system call failed: Connection refused.

This is firewall-cmd --list-all result:

public (active) target: default icmp-block-inversion: no interfaces: eno1 sources: services: dhcpv6-client ssh ports: protocols: forward: yes masquerade: no forward-ports: source-ports: icmp-blocks: rich rules: rule family="ipv4" source address="192.168.49.1" accept rule family="ipv4" source address="192.168.42.0/24" accept rule family="ipv4" source address="192.168.49.0/24" accept rule family="ipv4" source address="192.168.49.1/24" accept rule family="ipv4" source address="192.168.49.2" accept

I tried all the solutions i could find on your issues page.

Am i missing something? i've attached the logs

Attach the log file

minikube_mount_9105e281a57faf803ec5cff8e6b58b743301a1ed_0.log

Operating System

Ubuntu

Driver

Docker

StefanOid commented 4 months ago

Any comments please?

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 1 week ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

kubernetes / minikube