You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
packer/website/source/docs/other/environment-variables.html.md

2.4 KiB

description layout page_title sidebar_current
Packer uses a variety of environmental variables. docs Environment Variables - Other docs-other-environment-variables

Environment Variables for Packer

Packer uses a variety of environmental variables. A listing and description of each can be found below:

  • PACKER_CACHE_DIR - The location of the packer cache.

  • PACKER_CONFIG - The location of the core configuration file. The format of the configuration file is basic JSON. See the core configuration page.

  • PACKER_LOG - Setting this to any value other than "" (empty string) or "0" will enable the logger. See the debugging page.

  • PACKER_LOG_PATH - The location of the log file. Note: PACKER_LOG must be set for any logging to occur. See the debugging page.

  • PACKER_NO_COLOR - Setting this to any value will disable color in the terminal.

  • PACKER_PLUGIN_MAX_PORT - The maximum port that Packer uses for communication with plugins, since plugin communication happens over TCP connections on your local host. The default is 25,000. See the core configuration page.

  • PACKER_PLUGIN_MIN_PORT - The minimum port that Packer uses for communication with plugins, since plugin communication happens over TCP connections on your local host. The default is 10,000. See the core configuration page.

  • CHECKPOINT_DISABLE - When Packer is invoked it sometimes calls out to checkpoint.hashicorp.com to look for new versions of Packer. If you want to disable this for security or privacy reasons, you can set this environment variable to 1.

  • PACKER_TMP_DIR - The directory used for temporary files during marshalling. If unset, resolves to (unix: $HOME/.packer.d, windows: %USERPROFILE%/packer.d) or finally appending 'packer' to the value of os.TempDir() typically (unix: /tmp, windows: %TEMP% or %LOCALAPPDATA%). This is not to be confused with the provision target's temporary directory which is often hard-coded as /tmp or %SYSTEMROOT%/Temp in Provisioner modules or user-supplied template.