StefanScherer/docker-windows-box

[TODO] vmware-iso: Could not find networking conf file: /Library/Preferences/VMware Fusion/networking

timotheecour opened this issue · 7 comments

after #31 when I run:
packer build --only=vmware-iso windows_2016_docker.json
I get:

==> vmware-iso: Creating floppy disk...
vmware-iso: Copying files flatly from floppy_files
vmware-iso: Copying file: ./answer_files/2016_core/Autounattend.xml
vmware-iso: Copying file: ./scripts/disable-screensaver.ps1
vmware-iso: Copying file: ./scripts/disable-winrm.ps1
vmware-iso: Copying file: ./scripts/docker/enable-winrm.ps1
vmware-iso: Copying file: ./scripts/docker/2016/install-containers-feature.ps1
vmware-iso: Copying file: ./scripts/microsoft-updates.bat
vmware-iso: Copying file: ./scripts/win-updates.ps1
vmware-iso: Done copying files from floppy_files
vmware-iso: Collecting paths from floppy_dirs
vmware-iso: Resulting paths from floppy_dirs : []
vmware-iso: Done copying paths from floppy_dirs
==> vmware-iso: Creating required virtual machine disks
==> vmware-iso: Building and writing VMX file
==> vmware-iso: Could not find networking conf file: /Library/Preferences/VMware Fusion/networking
==> vmware-iso: Deleting output directory...
Build 'vmware-iso' errored: Could not find networking conf file: /Library/Preferences/VMware Fusion/networking

==> Some builds didn't complete successfully and had errors:
--> vmware-iso: Could not find networking conf file: /Library/Preferences/VMware Fusion/networking

==> Builds finished but no artifacts were created.

Thanks for the pull request.

VMware Fusion (Pro) needs a license. After installing it with brew cask install vmware-fusion you need to open the app at least once to start the 30 day trial. This also adds missing network cards vmnet1 and vmnet8.

I hope that helps.

thanks; after opening app and starting 30 day trial, still getting this error.
also tried hashicorp/vagrant#8285 (comment) with no success

I tried it in a fresh macOS.

  • install brew
  • brew install packer
  • brew cask install vmware-fusion
  • Open VMware Fusion
  • go into system preferences -> Security -> allow VMware, Inc.
  • quit VMware Fusion
  • open VMware Fusion again
  • ls "/Library/Preferences/VMware Fusion/networking" shows me that file.
  • after that I was able to run a packer build.

thanks! that did work :)
for the next steps:

  • brew cask install vagrant was needed (maybe add it to README?)

  • vagrant up failed with A Vagrant environment or target machine is required to run this
    so I ran vagrant init which creates a Vagrantfile; maybe mention it in README?

  • then: vagrant up gives:

No usable default provider could be found for your system.
Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.

not sure if I'm doing this right...

Thanks for the feedback.
When I started this repo I was years into Vagrant, so that's the difficult part writing a README.md for others that are just starting with Vagrant. :-)

As you go down the road with vmware-fusion you need to know that you will need a paid Vagrant VMware license, see https://www.vagrantup.com/vmware/index.html for more details.
You would need a helper ( brew cask install vagrant-vmware-utility) and the VMware plugin ( vagrant plugin install vagrant-vmware-desktop and vagrant license vagrant-vmware-desktop license.lic).

If you want to use Vagrant for free you could use VirtualBox (brew cask install virtualbox).

I don't know if all these steps can be covered in the README, as Vagrant can be used on at least three major OS (Windows, Mac, Linux) with different hypervisors.

Are you still going the VMware path or do you think it's easier for you to start with VirtualBox?

Closing due to inactivity.