Container Management

This chapter describes how you manage the containers used by CTERA Insight in both the proxy server and the CTERA Portal.

• Managing the Proxy Server Containers
• Managing the Portal Server Containers

Managing the Proxy Server Containers

Monitoring the Proxy Server Containers

Listing Running Containers

Run docker ps to list the containers currently running on the proxy server. The output from this command should include the following containers:

• kafka
• zookeeper
• metricbeat
• portal_logstash – Information from the portal
• gw-logstash – Information from the edge filer

Listing Containers That are Running or Have Run

Run docker ps -a to list both containers that have run and the containers currently running on the proxy server. The output from this command should include the list of containers that you get with ‘docker ps‘ and additionally the ‘proxyca‘ container which is responsible for entering the certificate to the proxy that is required for the edge filer to communicate with the proxy server.

Displaying Logs for a Container

Run docker logs -f container, for example docker logs -f proxyca, to check that there were no errors when the container started up and ran.
container is the name of the container as displayed in the output from docker ps -a.
The -f argument is optional and means that the last log entries are displayed in the output.

If a new certificate has been issues, errors will be displayed when running docker logs -f qw-logstash until he new certificate has been renewed.

Managing the Proxy Server Containers

The following set of commands must be run from /opt/ctera/insight/deploy/proxy/

Shutting Down the Proxy Containers

To shut down the containers running in the proxy server, run docker-compose down. This command stops all the CTERA Insight containers and the network and then removes the containers from the proxy server.

Starting Up the Proxy Containers

To start up the network and then the containers, including proxyca, which runs and then automatically shuts down, run docker-compose up -d. This command starts up the CTERA Insight default network and then the containers in the background.

Listing the Networks

To list the networks that are being used, run ‘docker network ls‘. This returns the list of networks with each network ID. You can use the network ID to list information about each container in the network.

Listing Container Information

To list the network subnet and gateway and the containers with additional information about each container, such as the container MAC address and IP address, run docker network inspect network_id where network_id is the NETWORK ID for the proxy_default network, listed using docker network ls

Managing the Portal Server Containers

The proxy server must have Internet access. The CTERA Portal does not require Internet access. If it does not have Internet access, the containers required for CTERA Insight are loaded to the CTERA Portal using a file daemon.json (/etc/docker/daemon.json), with the following content:

{
    "bip": "169.254.0.1/24",
    "default-address-pools":[
        {"base":"169.253.0.0/16","size":24},
        {"base":"169.252.0.0/16","size":24}
    ]
}

This file specifies where to get the CTERA Portal from the proxy server, 169.254.0.1 in the above example, and the containers will be taken from the pools 169.253.0.0 and 169.252.0.0 in the above example.

The CTERA Portal has the following containers which are used with CTERA Insight:

• filebeat_sci
• journalbeat_sci
• metricbeat_sci

All the commands described in Managing the Proxy Server Containers can be used for the portal containers from /opt/ctera/insight/server