github.com/hashicorp/packer@v1.14.3/website/content/docs/commands/plugins/install.mdx (about)

     1  ---
     2  description: |
     3    The `packer plugins install` command manually downloads and installs Packer plugins without having to update and initialize a build template. 
     4  page_title: packer plugins install command reference
     5  ---
     6  
     7  # `packer plugins install` command reference
     8  
     9  <Note>
    10  
    11  Starting August 1st, 2025, the source for many official HashiCorp-maintained Packer plugins is moving from GitHub releases to the official HashiCorp release site, [releases.hashicorp.com](https://releases.hashicorp.com). Refer to [Install HashiCorp-maintained plugins](/packer/docs/plugins/install#install-hashicorp-maintained-plugins) for more information.
    12  
    13  </Note>
    14  
    15  The `packer plugins install` command downloads and installs the most recent version of a plugin binary. Refer to [Installing Plugins](/packer/docs/plugins/install) for additional information about installing plugins.
    16  
    17  ## Description
    18  
    19  Use the `packer plugins install` command to manually install plugins instead of specifying plugins in a template and initializing Packer. Refer to the [`packer init` command documentation](/packer/docs/commands/init) for information about installing plugins specified in a Packer template during initialization.
    20  
    21  ### Third-party plugin verification
    22  
    23  HashiCorp only verifies plugins from GitHub under the`hashicorp/*` namespace. We recommend that you vet and verify any third-party plugins you want to install.
    24  
    25  ### Installation directory
    26  
    27  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. 
    28  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.
    29  Refer to the [Packer configuration reference](/packer/docs/configure) for additional information.
    30  
    31  ## Usage
    32  
    33  Use the following syntax to run the `packer plugins install` command:
    34  
    35  ## Examples
    36  
    37  Specify a version number to install a specific version of the plugin. The following example installs the version `1.0.1` of `my-plugin` from a remote source:
    38  
    39  ```shell-session
    40  $ packer plugins install github.com/hashicorp/my-plugin 1.0.1
    41  ```
    42  
    43  Use the `--path` option to specify a local plugin binary. The following example installs `my-plugin` from a local binary:
    44  
    45  ```shell-session
    46  $ packer plugins install --path my-plugin github.com/hashicorp/my-plugin
    47  ```
    48  
    49  ## Arguments
    50  
    51  You can pass the following arguments:
    52  
    53  - `<plugin-binary-source>`: A remote source where the plugin binary is available. To remotely download from a source, the plugin must be hosted on GitHub. For locally-sourced binaries, you must also include the `--path` option. Refer to [Installing Plugins](/packer/docs/plugins/install) for additional information about installing plugins.
    54  - `<plugin version>`: A specific version of the plugin to download and install. Packer accepts semantic version numbers that follow the `<major>.<minor>.<patch>` format. If omitted, the command installs the latest plugin version.
    55  
    56  ## Options
    57  
    58  You can use the following options:
    59  
    60  `--path`: Use this option to specify a local plugin binary. You must use this option to install plugins from a local source.
    61  `--force`: Use this option to force Packer to reinstall the plugin.
    62