Install Boundary using a package manager
Installing Boundary from the HashiCorp Linux Repository sets up the Boundary binary, a systemd service unit, and a dedicated boundary system user.
You can install the Boundary binary using a package manager, or manually install the binary and configure the Boundary service.
The steps vary by Linux distribution.
Enterprise
This feature requires Boundary Enterprise.
Complete the steps to install the binary:
Use the following command to add the HashiCorp GPG (GNU Privacy Guard) key as a trusted package-signing key:
$ curl -fsSL https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpgAdd the official HashiCorp Linux repository:
$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/hashicorp.listUpdate the package index:
$ sudo apt updateInstall Boundary Enterprise:
$ sudo apt install boundary-enterprise
Manually install Boundary
You can manually install a Boundary package from the HashiCorp Linux Repository, build Boundary from source, or get the package from another trusted location.
If you choose to install Boundary manually, ensure the Boundary packages you deploy on your controllers and workers in the next step are the same version. If you are deploying Boundary Enterprise, ensure you have a binary labeled ent.
You can review the following topics to manually configure systemd for the controllers and workers:
Troubleshooting
Common issues when installing Boundary using a package manager include:
- GPG key or repository signature mismatch: Confirm you added the HashiCorp GPG key and repository exactly as shown for your distribution, and that the keyring path referenced in your repository configuration matches the path used when you imported the key.
- Existing
boundarysystem user conflicts: If aboundaryuser or group already exists on the system from a previous install, the package installation may fail or behave unexpectedly. Remove or reconcile the existing user and group before reinstalling.
Next steps
After you install the binary, you should: