vagrant-address
vagrant-address copied to clipboard
On VirtualBox addresses are not resolved
Calling the command on VirtualBox machines Vagrant returns nothing. The issue is caused by Vagrant core: https://github.com/mitchellh/vagrant/issues/6729.
+1 :)
It seems that all related issues have been fixed. @mkuzmin what is the current state of the extension?
The bug in Vagrant core is still there, I've just checked 1.8.4.
If you don't use vagrant share
feature, then deleting the plugin helps:
rm -rf /opt/vagrant/embedded/gems/gems/vagrant-share-1.1.5/
I'll continue the conversation in the issue there.
This is broken in Vagrant v1.8.5 and VirtualBox 5.1.6. Deleting the share plugin simply results in vagrant address
returning 127.0.0.1
. I can use vagrant ssh
to access the VM.
Same here:
v-box> vagrant plugin install vagrant-address
Installing the 'vagrant-address' plugin. This can take a few minutes...
Fetching: vagrant-address-0.3.1.gem (100%)
Installed the plugin 'vagrant-address (0.3.1)'!
v-box> vagrant address v-box
127.0.0.1
v-box> vagrant ssh
$ /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 08:00:27:ba:0e:69
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:feba:e69/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:551 errors:0 dropped:0 overruns:0 frame:0
TX packets:352 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:60089 (58.6 KiB) TX bytes:51497 (50.2 KiB)
eth1 Link encap:Ethernet HWaddr 08:00:27:cb:b0:35
inet addr:10.10.1.248 Bcast:10.10.1.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fecb:b035/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:49 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4938 (4.8 KiB) TX bytes:1704 (1.6 KiB)
Interrupt:16 Base address:0xd040
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Hi, anyone has a workaround for Windows guests on Linux hosts? (You cannot use vagrant powershell
under Linux...)
Just installed this extension, but it seems this issue is still present? I still get 127.0.0.1
when there is also a public or private network