Closed spawnia closed 5 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
/remove-lifecycle stale
I have a similar issue with minikube 0.28.0 using VirtualBox :
minikube mount /Users:/Users
Mounting /Users into /Users on the minikube VM
This daemon process needs to stay alive for the mount to still be accessible...
ufs starting
running mount host command: ssh command error:
command :
sudo mkdir -p /Users || true;
sudo mount -t 9p -o trans=tcp,port=54230,dfltuid=1001,dfltgid=1001,version=9p2000.u,msize=262144 192.168.99.1 /Users;
sudo chmod 775 /Users;
err : Process exited with status 1
output : chmod: changing permissions of '/Users': Input/output error
By default /Users is a shared folders the virtualbox settings of the minikube VM, however I can't find it on the VM root system
Had this exact problem & I solved it by changing the Promiscuous mode to "Allow VMs" on Virtualbox
It does not solve my issue :(
@cscetbon just realized there is one step missing...
After configuring the Promiscuous mode to Allow VMs,
ipconfig
) and then, dominikube mount --ip <ip-of-attached-interface> c://Users//git//nice-project:/data/nice-project
I'm playing a lot with minikube, creating new instances with a different version of k8s each time. This really looks like a bug if we need to do so.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
Has anyone run into this with minikube (v0.33.x) and VirtualBox 6.x? I haven't heard anything in a while, so I wonder if this bug may be obsolete. If not, help wanted!
Unfortunately yes. I just ran into the issue with Minikube 0.33.1 and Virtualbox 6 (on a Windows 7 Machine).
It works when enabling promiscous mode and setting the ip explicitly as suggested by @snfaucher
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
I'm running into this as well, using minikube 1.0.1 and VirtualBox 6.0.6 on Windows 10.
Here's the information requested in #4098 before it was closed:
minikube mount --alsologtostderr -v=8 .:/kubebox
:
W0604 11:37:46.245502 35420 exit.go:99] Error getting the host IP address to use from within the VM: Error getting VM/Host IP address: Error finding IPV4 address for VirtualBox Host-Only Ethernet Adapter #2
! Error getting the host IP address to use from within the VM: Error getting VM/Host IP address: Error finding IPV4 address for VirtualBox Host-Only Ethernet Adapter #2
* Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
- https://github.com/kubernetes/minikube/issues/new
VBoxManage showvminfo minikube --machinereadable
:
name="minikube"
groups="/"
ostype="Linux 2.6 / 3.x / 4.x (64-bit)"
UUID="a7d44adc-75ae-40b5-b932-a639826ad8d7"
CfgFile="C:\\Users\\reck062\\.minikube\\machines\\minikube\\minikube\\minikube.vbox"
SnapFldr="C:\\Users\\reck062\\.minikube\\machines\\minikube\\minikube\\Snapshots"
LogFldr="C:\\Users\\reck062\\.minikube\\machines\\minikube\\minikube\\Logs"
hardwareuuid="a7d44adc-75ae-40b5-b932-a639826ad8d7"
memory=6192
pagefusion="off"
vram=8
cpuexecutioncap=100
hpet="on"
cpu-profile="host"
chipset="piix3"
firmware="BIOS"
cpus=4
pae="on"
longmode="on"
triplefaultreset="off"
apic="on"
x2apic="off"
nested-hw-virt="off"
cpuid-portability-level=0
bootmenu="disabled"
boot1="dvd"
boot2="dvd"
boot3="disk"
boot4="none"
acpi="on"
ioapic="on"
biosapic="apic"
biossystemtimeoffset=0
rtcuseutc="on"
hwvirtex="on"
nestedpaging="on"
largepages="on"
vtxvpid="on"
vtxux="on"
paravirtprovider="default"
effparavirtprovider="kvm"
VMState="running"
VMStateChangeTime="2019-06-04T09:03:48.169000000"
monitorcount=1
accelerate3d="off"
accelerate2dvideo="off"
teleporterenabled="off"
teleporterport=0
teleporteraddress=""
teleporterpassword=""
tracing-enabled="off"
tracing-allow-vm-access="off"
tracing-config=""
autostart-enabled="off"
autostart-delay=0
defaultfrontend=""
storagecontrollername0="SATA"
storagecontrollertype0="IntelAhci"
storagecontrollerinstance0="0"
storagecontrollermaxportcount0="30"
storagecontrollerportcount0="30"
storagecontrollerbootable0="on"
"SATA-0-0"="C:\Users\reck062\.minikube\machines\minikube\boot2docker.iso"
"SATA-ImageUUID-0-0"="40ee4860-9aaf-4393-9cc2-b4efed15ec72"
"SATA-tempeject"="off"
"SATA-IsEjected"="off"
"SATA-1-0"="C:\Users\reck062\.minikube\machines\minikube\minikube\Snapshots\{f9df0d7e-89f7-477c-be94-a71c6ca35069}.vmdk"
"SATA-ImageUUID-1-0"="f9df0d7e-89f7-477c-be94-a71c6ca35069"
"SATA-2-0"="none"
"SATA-3-0"="none"
"SATA-4-0"="none"
"SATA-5-0"="none"
"SATA-6-0"="none"
"SATA-7-0"="none"
"SATA-8-0"="none"
"SATA-9-0"="none"
"SATA-10-0"="none"
"SATA-11-0"="none"
"SATA-12-0"="none"
"SATA-13-0"="none"
"SATA-14-0"="none"
"SATA-15-0"="none"
"SATA-16-0"="none"
"SATA-17-0"="none"
"SATA-18-0"="none"
"SATA-19-0"="none"
"SATA-20-0"="none"
"SATA-21-0"="none"
"SATA-22-0"="none"
"SATA-23-0"="none"
"SATA-24-0"="none"
"SATA-25-0"="none"
"SATA-26-0"="none"
"SATA-27-0"="none"
"SATA-28-0"="none"
"SATA-29-0"="none"
natnet1="nat"
macaddress1="08002706D95A"
cableconnected1="on"
nic1="nat"
nictype1="virtio"
nicspeed1="0"
mtu="0"
sockSnd="64"
sockRcv="64"
tcpWndSnd="64"
tcpWndRcv="64"
Forwarding(0)="ssh,tcp,127.0.0.1,52906,,22"
hostonlyadapter2="VirtualBox Host-Only Ethernet Adapter #2"
macaddress2="0800277E436D"
cableconnected2="on"
nic2="hostonly"
nictype2="virtio"
nicspeed2="0"
nic3="none"
nic4="none"
nic5="none"
nic6="none"
nic7="none"
nic8="none"
hidpointing="ps2mouse"
hidkeyboard="ps2kbd"
uart1="off"
uart2="off"
uart3="off"
uart4="off"
lpt1="off"
lpt2="off"
audio="dsound"
audio_in="off"
audio_out="off"
clipboard="disabled"
draganddrop="disabled"
SessionName="headless"
VideoMode="720,400,0"@0,0 1
vrde="off"
usb="off"
ehci="off"
xhci="off"
SharedFolderNameMachineMapping1="c/Users"
SharedFolderPathMachineMapping1="\\\\?\\c:\\Users"
VRDEActiveConnection="off"
VRDEClients==0
videocap="off"
videocapaudio="off"
capturescreens="0"
capturefilename="C:\\Users\\reck062\\.minikube\\machines\\minikube\\minikube\\minikube.webm"
captureres="1024x768"
capturevideorate=512
capturevideofps=25
captureopts=""
GuestMemoryBalloon=0
GuestOSType="Linux26_64"
GuestAdditionsRunLevel=2
GuestAdditionsVersion="5.1.38 r122592"
GuestAdditionsFacility_VirtualBox Base Driver=50,1559639056142
GuestAdditionsFacility_VirtualBox System Service=50,1559639056277
GuestAdditionsFacility_Seamless Mode=0,1559639056142
GuestAdditionsFacility_Graphics Mode=0,1559639056142
SnapshotName="KubeBox mit Apps und Initialdaten"
SnapshotUUID="d16ef4f7-1eb9-491a-aeeb-6b9ea20bb4f8"
CurrentSnapshotName="KubeBox mit Apps und Initialdaten"
CurrentSnapshotUUID="d16ef4f7-1eb9-491a-aeeb-6b9ea20bb4f8"
CurrentSnapshotNode="SnapshotName"
SnapshotName-1="Sicherungspunkt 1"
SnapshotUUID-1="b53f614d-454d-4b63-a443-ecd1603088a8"
minikube ssh ip addr
:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 08:00:27:06:d9:5a brd ff:ff:ff:ff:ff:ff
inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic eth0
valid_lft 84341sec preferred_lft 84341sec
inet6 fe80::a00:27ff:fe06:d95a/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 08:00:27:7e:43:6d brd ff:ff:ff:ff:ff:ff
inet 192.168.99.109/24 brd 192.168.99.255 scope global dynamic eth1
valid_lft 938sec preferred_lft 938sec
inet6 fe80::a00:27ff:fe7e:436d/64 scope link
valid_lft forever preferred_lft forever
4: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0
5: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
link/ether 02:42:f7:27:d3:09 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
inet6 fe80::42:f7ff:fe27:d309/64 scope link
valid_lft forever preferred_lft forever
7: veth0292317@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether f6:1b:c1:dc:85:33 brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::f41b:c1ff:fedc:8533/64 scope link
valid_lft forever preferred_lft forever
9: veth0828b17@if8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether 66:fe:4d:30:ae:80 brd ff:ff:ff:ff:ff:ff link-netnsid 1
inet6 fe80::64fe:4dff:fe30:ae80/64 scope link
valid_lft forever preferred_lft forever
11: veth6c1b6e5@if10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether ea:34:64:5e:1f:a6 brd ff:ff:ff:ff:ff:ff link-netnsid 2
inet6 fe80::e834:64ff:fe5e:1fa6/64 scope link
valid_lft forever preferred_lft forever
13: vethc59f5c1@if12: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether b2:3c:85:00:a5:db brd ff:ff:ff:ff:ff:ff link-netnsid 4
inet6 fe80::b03c:85ff:fe00:a5db/64 scope link
valid_lft forever preferred_lft forever
15: veth739c3a0@if14: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether 3e:d8:31:46:f9:8e brd ff:ff:ff:ff:ff:ff link-netnsid 3
inet6 fe80::3cd8:31ff:fe46:f98e/64 scope link
valid_lft forever preferred_lft forever
17: veth85940f4@if16: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether 62:bf:3b:14:2e:e6 brd ff:ff:ff:ff:ff:ff link-netnsid 5
inet6 fe80::60bf:3bff:fe14:2ee6/64 scope link
valid_lft forever preferred_lft forever
19: veth6ae2838@if18: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether 46:78:4e:98:a7:23 brd ff:ff:ff:ff:ff:ff link-netnsid 6
inet6 fe80::4478:4eff:fe98:a723/64 scope link
valid_lft forever preferred_lft forever
21: veth9e9a20d@if20: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether b6:6f:4d:fc:19:66 brd ff:ff:ff:ff:ff:ff link-netnsid 7
inet6 fe80::b46f:4dff:fefc:1966/64 scope link
valid_lft forever preferred_lft forever
23: veth0a441e6@if22: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
link/ether ce:ea:53:5a:82:64 brd ff:ff:ff:ff:ff:ff link-netnsid 8
inet6 fe80::ccea:53ff:fe5a:8264/64 scope link
valid_lft forever preferred_lft forever
ipconfig /all
:
--- snip ---
Ethernet-Adapter VirtualBox Host-Only Network:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physische Adresse . . . . . . . . : 0A-00-27-00-00-04
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . : fe80::9153:fb10:39:4ab2%4(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.56.1(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . :
DHCPv6-IAID . . . . . . . . . . . : 118095911
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-24-59-CB-FD-54-EE-75-18-47-0C
DNS-Server . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS über TCP/IP . . . . . . . : Aktiviert
Ethernet-Adapter VirtualBox Host-Only Network #2:
Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter #2
Physische Adresse . . . . . . . . : 0A-00-27-00-00-0C
DHCP aktiviert. . . . . . . . . . : Nein
Autokonfiguration aktiviert . . . : Ja
Verbindungslokale IPv6-Adresse . : fe80::e858:f566:5e20:7b80%12(Bevorzugt)
IPv4-Adresse . . . . . . . . . . : 192.168.99.1(Bevorzugt)
Subnetzmaske . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . :
DHCPv6-IAID . . . . . . . . . . . : 436863015
DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-24-59-CB-FD-54-EE-75-18-47-0C
DNS-Server . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS über TCP/IP . . . . . . . : Aktiviert
--- snap ---
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /close
@fejta-bot: Closing this issue.
Bug Report
Please provide the following details:
Environment:
Minikube version (use
minikube version
): v0.24.1cat ~/.minikube/machines/minikube/config.json | grep DriverName
): virtualbox (v5.2.6)cat ~/.minikube/machines/minikube/config.json | grep -i ISO
orminikube ssh cat /etc/VERSION
): v0.23.6What happened: I tried mounting a folder from my host machine into minikube via
minikube mount C:\Users\Benedikt\projects\:/projects
This failed with the following error message:
I then followed the workaround mentioned in #1473 and renamed the Network Interface according to what the error output showed. After this, i could correctly mount the folder and access the files from within minikube.
What you expected to happen: The mount correctly executes and my host files are available in Minikube.
How to reproduce it (as minimally and precisely as possible): Try mounting a volume into minikube with virtualbox provider.