Documentation forOrion Platform

Docker Swarm requirements, deployment script examples, and container removal steps

This Orion Platform topic applies only to the following products:


Docker Swarm is one of the environments supported by the Container Monitoring feature.

To monitor Docker Swarm containers in the Orion Platform, you'll need:

  • Docker Engine 17.12 or later
  • Docker Compose file format 3.5 or later
  • SSH access to the master server
  • Sudo privileges on the master server
  • A weaveworks/scope:1.8.0 image in the Docker repository.

Required ports include:

  • 4043: Container port (internal Docker communication).
  • 6784: Report/wave status (internal Docker communication).
  • 80: Used to download the configuration file from the Orion server.

    An alternative to using port 80 is to download the file manually and send it to the Docker host.

Docker Swarm installation script

When you add a container service, the Add Container Service wizard generates a script that you can copy to the Windows Clipboard. Connect to the master server via SSH, open a command line, and run the script, which looks something like this:

curl -o cman-swarm.yaml #endpoint#
sed -i \"s/%HOSTNAME%/$(hostname)/g\" cman-swarm.yaml
sudo docker stack deploy -c cman-swarm.yaml sw

The script downloads the cman-swarm.yaml file, sets the hostname in the file to the master server, and starts a service named "sw" to deploy an sw_orionmonitor container to each server in the swarm.

Delete Docker Swarm containers and container images from nodes

Before you delete a container service in the Orion Web Console, remove Orion containers and images from the nodes (or cluster of nodes) manually.

  1. Connect to the node via SSH.
  2. Run the following command to remove the sw_orionaggregator and sw_orionmonitor containers:
    sudo docker service rm sw_orionaggregator
    sudo docker service rm sw_orionmonitor
  3. Run the following command to get a list of images and note the IDs for and weaveworks/scope:latest.
    sudo docker images
  4. Run the following command for each image:
    sudo docker rmi [image_id]

The service status switches to Down on the Container Services page. Now you can delete the container service by selecting its check box and clicking Delete.

The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.