you should try setting your temp directory to something shorter. This can be
done through the `TMPDIR` environment variable.
## Issues when temp directory does not allow execution
Sometimes, Packer runs into trouble (eg: when installing a plugin ) because the
system's temporary directory (/tmp) is restricted and doesn't allow programs to run there.
The temp directory may have been mounted with noexec option. This may lead to `permisson denied` errors.
```text
Continuing to next available version: failed to describe plugin binary "/tmp/packer-plugin-virtualbox_v1.1.1_x5.0_linux_arm64": fork/exec /tmp/packer-plugin-virtualbox_v1.1.1_x5.0_linux_arm64: permission denied
```
To resolve this, set the `TMPDIR` environment variable to a directory that allows execution.
@ -27,8 +27,8 @@ Note that Packer checks the plugin installation directory against the `required_
### Installation directory
By default, Packer installs plugins into the plugins directory at `$HOME/.config/packer/plugins` on Unix and `%APPDATA%\packer.d\plugins` on Windows, but you can specify a different directory using the `PACKER_PLUGIN_PATH environment variable.
Plugin installation requires access to temporary files under `TMPDIR`. If the system's temp directory is non-writable or non-executable, use TMPDIR to override the location of the temporary file store used by Packer.
By default, Packer installs plugins into the plugins directory at `$HOME/.config/packer/plugins` on Unix and `%APPDATA%\packer.d\plugins` on Windows, but you can specify a different directory using the `PACKER_PLUGIN_PATH` environment variable.
~> Note: Plugin installation requires access to temporary files under `TMPDIR`. If the system's temp directory is non-writable or non-executable, use TMPDIR to override the location of the temporary file store used by Packer.
Refer to the [Packer configuration reference](/packer/docs/configure) for additional information.
Anurag Sharma
1 year ago