Let me know if you need anymore information. => Builds finished but no artifacts were created. => Some builds didn't complete successfully and had errors: => hyperv-iso: Deleting build directory.īuild 'hyperv-iso' errored: error downloading ISO: => hyperv-iso: Deleting output directory. => hyperv-iso: leaving retrieve loop for ISO => hyperv-iso: Download failed mkdir c:\vcs\tfs\vista\devinfrastructure\\build\temp\packer-cache\c:: The filename, directory name, or volume label syntax is incorrect. Doesn't happen with Packer v1.3.5, v1.4.0 fails with a different error (empty checksum).Also fails if I remove the custom cache dir (uses build dir, same error).PACKER_CACHE_DIR is configured to S:\Vagrant\packer_cache.When I set the guest_additions_sha256 option explicitly it works fine, the guest additions iso itself is downloads fine and the build continues.Ĭreated a cut down template, it fails straight away on my setup If you prefer, you can install the oldest virtualbox-5.2.Īccording to your distribution, replace xenial with any other Ubuntu release, like zesty, yakkety, xenial, vivid, utopic, trusty, raring, quantal, precise, stretch, lucid, jessie, wheezy, or squeeze.8 15:37:42 ui: => virtualbox-iso: Retrieving Guest additions checksumsĨ 15:37:42 ui: => virtualbox-iso: Trying Ĩ 15:37:42 packer.exe: 8 15:37:42 Acquiring lock for: (S:\Vagrant\packer_cache\C:\Users\sbcdb\AppData\Local\Temp\packer886137615.lock)Ĩ 15:37:42 ui: => virtualbox-iso: Download failed mkdir S:\Vagrant\packer_cache\C:: The filename, directory name, or volume label syntax is incorrect.Ĩ 15:37:42 ui error: => virtualbox-iso: error downloading Guest additions checksums: Ĩ 15:37:42 ui: => virtualbox-iso: leaving retrieve loop for Guest additions checksums Ubuntu Host: run the following commands to register the repository with the package manager and update from it: sudo add-apt-repository "deb xenial contrib" Windows Host: Download from Virtualbox Download page for latest.
Note: Menu Help > Check for updates may not reflect the newest as being the latest. It has improved compatibility with Windows 10. Use of Windows Compatibility settings (or use /force) will not work: installer will run, but with no real effects.
0 kommentar(er)
