minikube mount fails with status 32 under RHEL 8

[raystorm]

When I try to mount a directory with

minikube mount /opt/nuxeo:/opt/nuxeo

I get the following error message:

• Mounting host path /opt/nuxeo into VM as /opt/nuxeo ...
• Mount options:
  
  
  
  • Type: 9p
  
  
  • UID: docker
  
  
  • GID: docker
  
  
  • Version: 9p2000.L
  
  
  • MSize: 262144
  
  
  • Mode: 755 (-rwxr-xr-x)
  
  
  • Options: map[]
  
  
• Userspace file server: ufs starting

X mount failed: mount: /opt/nuxeo: mount(2) system call failed: Connection refused.
: Process exited with status 32

• Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
  
  
  
  • https://github.com/kubernetes/minikube/issues/new
  
  

I'm running the command as root on under Red Hat Enterprise Linux 8,
and minikube is configured to use the kvm2 vm-driver.

Additionally, I just upgraded to version v.1.2.0

[afbjorklund]

Usually network related. Can you try without the firewalld ?

[raystorm]

@afbjorklund,

This is my current Firewall config for libvirt the zone minikube should be using.

[root@sawinsknaxnox ~]# firewall-cmd --zone=libvirt --list-all
libvirt (active)
target: ACCEPT
icmp-block-inversion: no
interfaces: virbr0 virbr1
sources:
services: dhcp dhcpv6 dns http ssh tftp
ports: 80/tcp 8080/tcp 27017/tcp
protocols: icmp ipv6-icmp
masquerade: no
forward-ports:
source-ports:
icmp-blocks:
rich rules:
rule priority="32767" reject

Is there something I need to change? I'd rather not completely disable the firewall unless I absolutely have to, as my server is internet facing.

[afbjorklund]

Might be tricky, I think 9p uses random ports. Just wondered if it was the one blocking the traffic...

Compare #2300

[raystorm]

I took at look at the issue you linked. The final comment was really helpful.

adding

firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="192.168.39.0/24" accept'

Didn't work

but adding

firewall-cmd --permanent --zone=libvirt --add-rich-rule='rule family="ipv4" source address="192.168.39.0/24" accept'

DID Work

NOTE: for reference I did do a firewall-cmd --reload after each rule command before testing minikibe mount to see if it worked.

Thank you

[kaspro]

I want to amend here that the same issue - as well as solution - is true for Fedora 31.

[fiskhest]

I'm using arch linux and ran into the same issue. Allowing source net 192.168.39.0/24 as commented above did not work, but allowing 192.168.99.0/24 did:

sudo firewall-cmd --permanent --zone=libvirt --add-rich-rule='rule family="ipv4" source address="192.168.99.0/24" accept'
sudo firewall-cmd --reload

[chokhareganesh]

What is the solution if I'm using VirtualBox to run minikube

[blueelvis]

@raystorm @kaspro @fiskhest - Thank you for the confirmation! This should be added to our documentation. Up for grabs!

@chokhareganesh - Could you please open a different issue describing your issue? Thanks!