How jacobalberty/unifi-docker works
This repository packages Ubiquiti’s UniFi Network Controller as a Docker container; it does not implement the controller’s application logic. The main workflow is an operator starting the container with configuration and persistent storage, then reaching the controller through its web interface and allowing UniFi devices to contact it using the Docker host’s address. The README documents those relationships, including ports, volumes, and SYSTEM_IP. Source excerpts were unavailable, so internal startup and health-check behavior is not inferred.
Main entry points: Dockerfile UniFi image
Components 11
Container runtime
- UniFi image
Dockerfile - Container entrypoint
docker-entrypoint.sh - Health check
docker-healthcheck.sh
Controller access
- UniFi Controller
- Published ports
Configuration and state
- Host data directory
- Container data mount
- Docker host address
Other components
- Docker operator
- Administrator browser
- UniFi devices
Connections 7
- Docker operator → UniFi image: starts container
README.md - UniFi image → UniFi Controller: runs bundled
README.md - Host data directory → Container data mount: persists files
README.md - Administrator browser → Published ports: connects through
README.md - Published ports → UniFi Controller: exposes interface
README.md - UniFi devices → Docker host address: reach controller at
README.md - Docker host address → UniFi Controller: configured as SYSTEM_IP
README.md