We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All provisioning scripts run on all builders, so that both parallels.sh and vmware.sh run on virtualbox-iso builder.
parallels.sh
vmware.sh
Do a build with with -only option, e.g. packer build -only=vmware-iso.
-only
packer build -only=vmware-iso
Onlyvirtualbox.sh provisioning script would run. The vmware.sh and parallels.sh scripts would NOT run.
virtualbox.sh
All three vm platform specific provisioning scripts (parallels, vmware, virtualbox) would run on virtualbox.
Use {{.Provider}} in the name (haven't tried this):
{{.Provider}}
{ "type": "shell", "execute_command": "chmod +x {{ .Path }}; {{ .Vars }} sudo -E -S bash '{{ .Path }}'", "scripts": [ "script/{{.Provider}}.sh", "script/xcode-cli-tools.sh", "script/add-network-interface-detection.sh", "script/energy.sh", "script/autologin.sh", "script/update.sh", "script/update.sh", "script/update.sh", "script/update.sh" ], }
Utilize the only key within a provisioners area:
only
{ "only": ["virtualbox-iso"], "type": "shell", "execute_command": "chmod +x {{ .Path }}; {{ .Vars }} sudo -E -S bash '{{ .Path }}'", "script": "scripts/virtualbox.sh" }
The text was updated successfully, but these errors were encountered:
No branches or pull requests
All provisioning scripts run on all builders, so that both
parallels.sh
andvmware.sh
run on virtualbox-iso builder.STEPS
Do a build with with
-only
option, e.g.packer build -only=vmware-iso
.EXPECTED RESULTS
Only
virtualbox.sh
provisioning script would run.The
vmware.sh
andparallels.sh
scripts would NOT run.ACTUAL RESULTS
All three vm platform specific provisioning scripts (parallels, vmware, virtualbox) would run on virtualbox.
POTENTIAL SOLUTIONS
Use
{{.Provider}}
in the name (haven't tried this):Utilize the
only
key within a provisioners area:The text was updated successfully, but these errors were encountered: