Manually Adding a Beacon Container

As of V2.2, Beacon is now a standard feature of the VIP system and is used to send email invitations during the connection process. The instructions below can be used to add the Beacon container to earlier versions of VIP.

Note that this section will only cover setting up the Beacon container. For more information on how to configure the internals of the Beacon server, see the "VIP Beacon and Invitation Server" section.

Figure 1 - Adding the Beacon container

Next, add two volumes - one writeable and one read-only - as shown below in Figure 19:

Figure 2 - Adding volumes

Set the hostname and IP address of the Beacon container as shown below in Figure 20:

Figure 3 - Beacon hostname and IP address

Click the "Deploy the container" button when finished. Connect to the Beacon container using <BeaconContainerIP>.

Container Startup Policy

To adjust whether a container such as Dashboard or ViPX automatically runs, the restart policy must be configured for each container.

Select the relevant container, then click on “duplicate/edit”.

Figure 4- Editing container details

The "Restart policy" is located at the bottom of the page and offers the following options:

• Never: The container does not automatically restart and must be manually started after the VM has booted. This is the default behavior.

• Always: The container always restarts if it stops. If it is manually stopped, it restarts only when the Docker daemon restarts or when it is manually restarted.

• On failure: The container restarts if it closes due to an error that manifests as a non-zero exit code.

• Unless stopped: Similar to “Always” except that when the container is stopped (manually or otherwise), it is not re-started even after the Docker daemon restarts.

Figure 5 - Container restart policy