Understanding the docker run command - Adaptive Plugins - BlueCat Gateway - 20.3.0

ExtraHop Administration Guide

BlueCat Gateway

The following table describes the different code segments and variables of the docker run command:

Code Segment: Description
docker run This section is used to run a command in a new Docker container.
-d This flag indicates that the Docker container runs in the detached mode. The Docker container runs in your terminal background and does not receive and input or display any output.
-p <http_port>:8000 -p <https_port>:44300
This variable specifies the allocation of external ports to use:
  • Port 8000 in the container is allocated to the defined <http_port> on the Docker host.
  • Port 44300 in the container is allocated to the defined <https_port> on the Docker host.
-v <path_to_mapped_log_directory_for_system_logs>:/logs/ This variable maps a Docker logs volume (recommended) or a logs directory on your local machine.
-e BAM_IP=<your_bam_ip_address> This environment variable is used to specify the Address Manager server's IP address that you wish to integrate with Gateway. You must enter the Address Manager IP as an environment variable when running the Gateway container for the first time.
--name <gateway_container_name> This variable indicates the name of the container. By default, the name of the container is bluecat_gateway; however, you can change this to reflect the needs of your environment.
quay.io/bluecat/extrahop:20.3 This section refers to the Gateway image tag from which the container will be created.
  • If the image has already been pulled and is available locally, the container will be created from that image.
  • If the image is not available locally, it will be pulled from the Quay.io cloud registry.