Thank you for this.
Apologies, I tried many different things before posting and none of them
worked. Regarding you link with vagrant file like this:
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant.configure("2") do |config|
config.vm.box = "StefanScherer/windows_2016_docker"
config.vm.network "public_network", adapter: "0"
config.vm.provider :vmware_workstation do |v|
v.gui = true
end
end
The error I'm getting is this:
Bringing machine 'default' up with 'vmware_workstation' provider...
==> default: Cloning VMware VM: 'StefanScherer/windows_2016_docker'. This
can take some time...
==> default: Checking if box 'StefanScherer/windows_2016_docker' is up to
date...
==> default: Verifying vmnet devices are healthy...
==> default: Preparing network adapters...
WARNING: The VMX file for this box contains a setting that is automatically
overwritten by Vagrant
WARNING: when started. Vagrant will stop overwriting this setting in an
upcoming release which may
WARNING: prevent proper networking setup. Below is the detected VMX setting:
WARNING:
WARNING: ethernet0.pcislotnumber = "33"
WARNING:
WARNING: If networking fails to properly configure, it may require this VMX
setting. It can be manually
WARNING: applied via the Vagrantfile:
WARNING:
WARNING: Vagrant.configure(2) do |config|
WARNING: config.vm.provider :vmare_workstation do |vmware|
WARNING: vmware.vmx["ethernet0.pcislotnumber"] = "33"
WARNING: end
WARNING: end
WARNING:
WARNING: For more information:
https://www.vagrantup.com/docs/vmware/boxes.html#vmx-whitelisting
==> default: Starting the VMware VM...
==> default: Waiting for the VM to receive an address...
==> default: Forwarding ports...
default: -- 3389 => 3389
default: -- 22 => 2222
default: -- 5985 => 55985
default: -- 5986 => 55986
==> default: Waiting for machine to boot. This may take a few minutes...
==> default: Stopping the VMware VM...
==> default: Deleting the VM...
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/plugins/communicators/winrm/helper.rb:41:in
`winrm_info_invalid?': undefined method `start_with?' for 0:Integer
(NoMethodError)
from
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/plugins/communicators/winrm/helper.rb:36:in
`winrm_address'
from
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/plugins/communicators/winrm/helper.rb:21:in
`winrm_info'
from
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/plugins/communicators/winrm/communicator.rb:37:in
`block in wait_for_ready'
from
C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:93:in
`block in timeout'
from
C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:33:in
`block in catch'
from
C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:33:in
`catch'
from
C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:33:in
`catch'
from
C:/HashiCorp/Vagrant/embedded/mingw64/lib/ruby/2.4.0/timeout.rb:108:in
`timeout'
from
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/plugins/communicators/winrm/communicator.rb:31:in
`wait_for_ready'
from
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-2.0.1/lib/vagrant/action/builtin/wait_for_communicator.rb:16:in
`block in call'
from
C:/HashiCorp/Vagrant/embedded/gems/gems/logging-2.2.2/lib/logging/diagnostic_context.rb:474:in
`block in create_with_logging_context'
Did you ever actually got this working in practice, or is that a case of
"should work in principle"?
Cheers,
Andrew
On Monday, 20 November 2017 22:47:42 UTC+13, Alvaro Miranda Aguilera wrote:
>
> the first nic is by default.
>
> So you don't want to add a new nic, you can override the first one.
>
> have a look at this:
>
> https://superuser.com/questions/957631/how-to-force-vagrant-to-have-a-single-bridged-network-interface
>
> Alvaro
>
>
> On Mon, Nov 20, 2017 at 1:55 AM, <[email protected] <javascript:>> wrote:
>
>> When I add this line to my vagrantfile:
>>
>> config.vm.network "public_network", bridge: "vmnet0"
>>
>> vagrant creates *second* adapter which is bridged.
>> Both primary and secondary adaters seems to work fine in this
>> configuration.
>> I do not want second adapter I want the primary one to be bridged.
>>
>> How do I configure this?
>>
>> Vagrantfile to test:
>>
>> # -*- mode: ruby -*-
>> # vi: set ft=ruby :
>>
>> Vagrant.configure("2") do |config|
>> config.vm.box = "StefanScherer/windows_2016_docker"
>>
>> config.vm.network "public_network"
>> config.vm.provider :vmware_workstation do |v|
>> v.gui = true
>> end
>> end
>>
>>
>>
>> Cheers,
>> Andrew
>>
>> --
>> 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 [email protected] <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/vagrant-up/f564595c-48f5-4dc3-ae48-067f09b2da0f%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/vagrant-up/f564595c-48f5-4dc3-ae48-067f09b2da0f%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Alvaro
>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/30e5c933-2bd5-46c4-87dd-67fdfaf5e71d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
