# Docker Swarm Visualizer

Docker Swarm Visualizer is a self-hosted infrastructure app. A real-time web visualization tool for Docker Swarm clusters that helps homelab operators monitor and troubleshoot nodes, services, and networks as an interactive graph. It is open source and self-hosted, installable on Docker Hub and Unraid.

Canonical page: https://ourlocalhost.com/app/254/docker-swarm-visualizer

## Description

A real-time web visualization tool for Docker Swarm clusters that helps homelab operators monitor and troubleshoot nodes, services, and networks as an interactive graph.

## Platform availability

Available on 1 of 10 platforms: Unraid.

## Health score

25/100 (Low), based on 4 of 5 factors.
- Maintained: 0 (last commit 756 days ago)
- Popular: 70 (3,339 GitHub stars)
- Easy to install: 35 (1 install platform, install notes, Docker image)
- Security check: 10 (3 serious findings, 13 minor)

## Security check

3 serious findings: Uses form-data 2.1.4, which has a known critical vulnerability; Uses loader-utils 0.2.17, which has a known critical vulnerability; Uses proxy-addr 2.0.7, which has a known critical vulnerability.
Automated checks on commit 82bd663, 20 Oct 2026. Not an audit.

## Links

- GitHub: https://github.com/dockersamples/docker-swarm-visualizer
- Docker Hub: https://hub.docker.com/r/dockerswarmvisualizer/dockerswarmvisualizer
- Unraid: https://ca.unraid.net/apps/docker-swarm-visualizer-1d9088s1clfwqw?q=Docker-Swarm-Visualizer
- Official website: https://sammonsempes.github.io/DockerSwarmVisualizer/

## Common questions

### Why does the visualizer container start but show no Swarm nodes?

Start it on the correct Docker network using --network=<name>. If it is not connected to that network, it may start but cannot see the Docker Swarm nodes it needs to visualize.

### What should I do if port 8080 is already used on the host?

Map a different host port to container port 8080, such as -p 5000:8080. The container still listens on 8080 internally.

### How do I run it with a different context root when behind an external load balancer?

Set the CTX_ROOT environment variable to the desired path, for example CTX_ROOT=/visualizer. This makes the app use that root context.

### Is the app safe to expose as-is in production?

The project notes that running it in production is insecure because it is a sample app. If you run it anyway, take security precautions and protect the Docker daemon socket with SSL.

### How do I run it as a Docker Swarm service?

Create a service with --publish=8080:8080/tcp and a constraint for manager nodes. It also needs a bind mount of /var/run/docker.sock.

---
Source: Our Local Host (https://ourlocalhost.com/app/254/docker-swarm-visualizer), the self-hosted and open-source app directory.
