hashicorp/boundary-enterprise pulls statistics

<!--- This is used for the Overview tab for the boundary-enterprise docker image on hub.docker.com https://hub.docker.com/r/hashicorp/boundary-enterprise

Boundary Enterprise

Disclaimer

This HashiCorp enterprise software is for use only by customers who have a valid and active license agreement with HashiCorp or an authorized HashiCorp reseller. If you do not have a valid license to use this software, you may not download or otherwise use it. All use of this software is subject to the terms and conditions of your license agreement, and all other rights are expressly reserved.

Agreement

The following shall apply unless your organization has a separately signed agreement governing your use of the software made available here:

The software is subject to the license terms or community license (i.e. Mozilla Public License 2.0 or Business Source License), as applicable, located in the download package for the software, the IBM International Program License Agreement, the IBM International License Agreement for Evaluation of Programs (for evaluation uses), or the IBM International License Agreement for Early Release of Programs (alpha and beta releases), and the applicable License Information, copies of which are also available at https://www.ibm.com/terms. In the event of a conflict between the license file in the download package and the noted IBM licenses above, the relevant IBM terms will apply. Please refer to the license terms prior to using the software. Your installation and use of the software constitute your acceptance of those terms. If you do not accept the terms, do not use the software.

Usage

Dev Mode

Due to the limitations of boundary dev running and maintaining a postgres docker container, it's not recommended to run dev mode inside docker. To do so will require knowledge of running docker-in-docker, and the caveats associated with it.

Default Configuration

The default behavior of the Boundary docker image is to run boundary server -config /boundary/config.hcl. The included config.hcl file is meant to serve as an example, and is not suitable for actual deployment. Please see the comments within the file for more information; full configuration details can be found on Boundary's documentation site.

Postgres

The usage instructions in this README assume you have an external postgres database (version 12 or greater) to run boundary server with. If you want to get started quickly, you can start a local postgres in docker:

The postgres URL setting is defined with env://BOUNDARY_POSTGRES_URL so it can be easily set with -e during docker run:

Controller

If using the image for a boundary controller, or controller and worker combination, a valid license must be supplied. The license can be provided as an environment variable:

Or it can be specified in a custom config.hcl (assuming config.hcl is located at $(pwd)/config.hcl):

config.hcl:

Database Init

If you're starting with a new, unused postgres instance, initialize the database using the default config.hcl:

If you want to run this with your own config.hcl (assuming config.hcl is located at $(pwd)/config.hcl):

Database Migration

If you are updating to a newer version of boundary with a database instance that was initialized with an older version, you will need to apply the database migrations:

If you want to run this with your own config.hcl (assuming config.hcl is located at $(pwd)/config.hcl):

Server

Start a Boundary server using the default config.hcl:

Start a Boundary server using your own config.hcl, assuming it's located at $(pwd)/config.hcl:

Worker

If using this image as a worker, either a worker that will connect to a boundary-enterprise controller, or as a Self-Managed Worker with HCP Boundary, It is not necessary to provide the license via an environment variable or config, however the worker must connect with a licensed controller.

Assuming a config.hcl located at $(pwd)/config.hcl:

config.hcl:

Description from the Docker Hub listing.