Hi everyone (who actually uses the vagrant-vmware-workstation plugin).
I'm currently struggling with the vagrant-vmware-workstation plugin and who
it establishes the ssh connection.
In contrast to the virtualbox provider, it does not use 127.0.0.1 with the
auto-forwarded port for connecting, but uses some (non-deterministic)
nat'ed ip address as far as I can tell:
Y:\tmp>vagrant up --provider vmware_workstation
Bringing machine 'default' up with 'vmware_workstation' provider...
==> default: Cloning VMware VM: 'boxcutter/ubuntu1604'. This can take some
time...
==> default: Verifying vmnet devices are healthy...
==> default: Preparing network adapters...
*==> default: Fixed port collision for 22 => 2222. Now on port 2200.*
==> default: Starting the VMware VM...
==> default: Waiting for machine to boot. This may take a few minutes...
*default: SSH address: 192.168.153.175:22 <http://192.168.153.175:22>*
default: SSH username: vagrant
default: SSH auth method: private key
default:
default: Vagrant insecure key detected. Vagrant will automatically
replace
default: this with a newly generated keypair for better security.
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH
key...
==> default: Machine booted and ready!
*==> default: Forwarding ports...*
* default: -- 22 => 2200*
==> default: Configuring network adapters within the VM...
==> default: Waiting for HGFS to become available...
==> default: Enabling and configuring shared folders...
default: -- Y:/tmp: /vagrant
==> default: Running provisioner: shell...
default: Running: inline script
==> default: mesg:
==> default: ttyname failed
==> default: :
==> default: Inappropriate ioctl for device
==> default: wohooo
This causes some issues for us, especially when additional network adapters
are added inside the guest VM, which causes the vmware workstation plugin
to randomly pick the wrong one for establishing the ssh connection and thus
can't connect.
While we have created support tickets at http://support.hashicorp.com for
that already (#2639, #2462), I'd also like to ask in the community if you
encountered similar issues, or found a way to force vagrant using the
localhost forwarded ssh port somehow.
I had tried forcing the ssh connection via 127.0.0.1 and the
config.ssh.guest_port
<https://www.vagrantup.com/docs/vagrantfile/ssh_settings.html> setting, but
this did not work because the actual port forwarding happens only after the
initial ssh connection / key insertion (with the virtualbox provider it
happens right in the beginning).
Any ideas, similar pain points with vagrant-vmware-workstation, or
suggested workarounds?
Cheers,
Torben
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/CACN%2Ba_bNV%2BGCr-jDz0DX5-s_g%3DAD4P2DJ0uBqJf1EoPkghhZJQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
