File not found
KevinBurton opened this issue · 4 comments
KevinBurton commented
I try to install a Windows Docker machine and I get the following output
Rs-MacBook-Pro:packer-windows rebeccaannburton$ ./build_windows_2016_docker.sh
vmware-iso output will be in this color.
==> vmware-iso: Downloading or copying ISO
vmware-iso: Downloading or copying: file:///Users/rebeccaannburton/projects/packer-windows/iso/en_windows_server_2016_updated_feb_2018_x64_dvd_11636692.iso
==> vmware-iso: Creating floppy disk...
vmware-iso: Copying files flatly from floppy_files
vmware-iso: Copying file: ./answer_files/2016/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 virtual machine disk
==> vmware-iso: Building and writing VMX file
==> vmware-iso: Starting virtual machine...
I also get a dialog box that says 'File not found'
The script I am using looks like:
packer build \
--only=vmware-iso \
--var vhv_enable=true \
--var iso_url=./iso/en_windows_server_2016_updated_feb_2018_x64_dvd_11636692.iso \
--var iso_checksum=7ADC82E00F1367B43897BB969A75BBF96D46F588 \
--var iso_checksum_type=sha1 \
--var autounattend=./answer_files/2016/Autounattend.xml \
windows_2016_docker.json
I am using Fusion 10.1.1. Any idea what is wrong?
StefanScherer commented
Looks good so far.
Which version of Packer do you use?
You can run Packer with more debug logging.
export PACKER_LOG=1
Does packer work with other templates?
KevinBurton commented
packer --version
1.1.2
StefanScherer commented
Packer 1.2.3 has been released. Maybe it‘s working better with this version.
But it looks like an issue with VMware itself
StefanScherer commented
Closing. Seems like a VMware problem.