Docker Swarm Visualizer
A real-time web visualization tool for Docker Swarm clusters that helps homelab operators monitor and troubleshoot nodes, services, and networks as an…
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
25/100 Low
- Maintained
- 0last commit 756 days ago
- Popular
- 703,339 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
- Security check
- 103 serious findings, 13 minor
Based on 4 of 5 factors.
Security check: 3 serious findings
- Uses form-data 2.1.4, which has a known critical vulnerability (npm)
- Uses loader-utils 0.2.17, which has a known critical vulnerability (npm)
- Uses proxy-addr 2.0.7, which has a known critical vulnerability (npm)
Automated checks on commit 82bd663, 20 Oct 2026. Not an audit.
Availability: platform listings confirmed today, links checked 55 days ago
- GitHub stars
- 3,339
- Open issues
- 11
- Last commit
- 2024-10-26
- License
- Apache-2.0
- Activity
- stale
Checked 21 days ago - source: GitHub (dockersamples/docker-swarm-visualizer)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Attach it to the right network When starting the visualizer container, add --network=<name> to put it on the Docker network (the private group of containers that can talk to each other). If it isn't connected, it may start but can't see the Docker Swarm nodes it needs to visualize. source
Fetched 54 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
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.
Answers sourced from github.com, github.com
Community
- DockerSwarm - Reddit (reddit)
- Need to grow my setup - Docker standalone, Swarm or Kubernetes? - Reddit (reddit)
- Is Docker swarm visualizer viable on-premises? : r/docker - Reddit (reddit)
- Swarmlet - A self-hosted, open-source Platform as a Service ... - Reddit (reddit)
- Docker swarm in a home lab? : r/selfhosted - Reddit (reddit)
- Is Docker Swarm really dead … : r/selfhosted - Reddit (reddit)
Collected 48 days ago - public community threads