minikube: Minikube mount fails in v0.19.0

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Minikube version (use minikube version): v0.19.0

Environment:

  • OS : Ubuntu 16.04.2 LTS (Xenial Xerus)
  • VM Driver: virtualbox
  • ISO version : v0.18.0

What happened: minikube mount command fails in v0.19.0, which was working in minikube v0.18.0. It exits with error:

E0510 14:28:27.988073    6989 mount.go:91] Error getting the host IP address to use from within the VM:  Error getting VM/Host IP address: Error finding IPV4 address for vboxnet0

What you expected to happen: Expected the host directory to be mounted within minikube VM

How to reproduce it (as minimally and precisely as possible):

  1. Start the cluster minikube start --insecure-registry="192.168.0.2:5000" --memory 4096 --vm-driver="virtualbox"
  2. Try mounting a dir:
wrkstn$ minikube mount /home/myuser/src:/src
E0510 14:28:27.988073    6989 mount.go:91] Error getting the host IP address to use from within the VM:  Error getting VM/Host IP address: Error finding IPV4 address for vboxnet0

Anything else do we need to know:

wrkstn$ kubectl describe node 
Name:			minikube
Role:			
Labels:			beta.kubernetes.io/arch=amd64
			beta.kubernetes.io/os=linux
			kubernetes.io/hostname=minikube
Annotations:		node.alpha.kubernetes.io/ttl=0
			volumes.kubernetes.io/controller-managed-attach-detach=true
Taints:			<none>
CreationTimestamp:	Wed, 10 May 2017 14:10:31 +0530
Phase:			
Conditions:
  Type			Status	LastHeartbeatTime			LastTransitionTime			Reason				Message
  ----			------	-----------------			------------------			------				-------
  OutOfDisk 		False 	Wed, 10 May 2017 15:41:46 +0530 	Wed, 10 May 2017 14:10:31 +0530 	KubeletHasSufficientDisk 	kubelet has sufficient disk space available
  MemoryPressure 	False 	Wed, 10 May 2017 15:41:46 +0530 	Wed, 10 May 2017 14:10:31 +0530 	KubeletHasSufficientMemory 	kubelet has sufficient memory available
  DiskPressure 		False 	Wed, 10 May 2017 15:41:46 +0530 	Wed, 10 May 2017 14:10:31 +0530 	KubeletHasNoDiskPressure 	kubelet has no disk pressure
  Ready 		True 	Wed, 10 May 2017 15:41:46 +0530 	Wed, 10 May 2017 14:10:31 +0530 	KubeletReady 			kubelet is posting ready status
Addresses:		192.168.99.100,192.168.99.100,minikube
Capacity:
 cpu:		2
 memory:	4046840Ki
 pods:		110
Allocatable:
 cpu:		2
 memory:	3944440Ki
 pods:		110
System Info:
 Machine ID:			4cd8ff42d41644d9a529dd244dfd09
 System UUID:			9C3E6FD0-B88A-473F-9000-5F2E2A4FF2B1
 Boot ID:			70f7908d-2e9b-4075-abcd-ee037313c89b
 Kernel Version:		4.7.2
 OS Image:			Buildroot 2016.08
 Operating System:		linux
 Architecture:			amd64
 Container Runtime Version:	docker://1.11.1
 Kubelet Version:		v1.6.0
 Kube-Proxy Version:		v1.6.0
ExternalID:			minikube
Non-terminated Pods:		(5 in total)
  Namespace			Name					CPU Requests	CPU Limits	Memory Requests	Memory Limits
  ---------			----					------------	----------	---------------	-------------
  kube-system			kube-addon-manager-minikube		5m (0%)		0 (0%)		50Mi (1%)	0 (0%)
  kube-system			kube-dns-268032401-6htv2		260m (13%)	0 (0%)		110Mi (2%)	170Mi (4%)
  kube-system			kubernetes-dashboard-hmjfx		0 (0%)		0 (0%)		0 (0%)		0 (0%)
  myapp			postgres-3189009613-f5bcs		0 (0%)		0 (0%)		0 (0%)		0 (0%)
  myapp			redis-3067652467-hr1r6			100m (5%)	0 (0%)		100Mi (2%)	0 (0%)
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  CPU Requests	CPU Limits	Memory Requests	Memory Limits
  ------------	----------	---------------	-------------
  365m (18%)	0 (0%)		260Mi (6%)	170Mi (4%)
Events:		<none>

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Reactions: 1
  • Comments: 18 (4 by maintainers)

Most upvoted comments

Work around for me: I renamed my interface to “VirtualBox Host-Only Ethernet Adapter #2” and minikube mount work! You must remove “interface” from your network interface name

I’m still having this problem with v0.21.0 on windows 10 with hyper-v

PS D:\Work> minikube mount d:/Work/data:/data
E0816 18:02:39.443496    6388 mount.go:113] Error getting the host IP address to use from within the VM:  Error getting VM/Host IP address: Error finding IPV4 address for vEthernet ()