vagrant-service-manager
vagrant-service-manager copied to clipboard
Private network is being set for unsupported box
Steps to Reproduce:
vagrant init debian/jessie64
Logs:
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'debian/jessie64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'debian/jessie64' is up to date...
==> default: Setting the name of the VM: test_default_1463904952697_76908
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
-----------------------------------------------------------------------------------
==> default: When using virtualbox, a non-NAT network interface is required.
==> default: Adding a private network using DHCP
-----------------------------------------------------------------------------------
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 (guest) => 2200 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2200
default: SSH username: vagrant
default: SSH auth method: private key
....
==> default: Machine booted and ready!
........
On uninstalling vagrant-service-manager, this issue get solved.
PR #229 is producing issue #235 and hence we are reverting the fix here #236. We will continuing to look for this issue alternative solution.