The UNiFi controller being phased out in favour of UniFi-OS-Server, have any of you been successful getting it to run in a Docker container?
Based on a recent docker image ( GitHub - lemker/unifi-os-server: Run UniFi OS Server in Docker or Kubernetes ), I’ve tried the following, in Dockge:
services:
unifi-os-server:
image: ghcr.io/lemker/unifi-os-server:latest
container_name: unifi-os-server
privileged: true
environment:
- UOS_SYSTEM_IP=unifi-os.home.net
volumes:
- ./unifi-os-server/persistent:/persistent
- ./unifi-os-server/var-log:/var/log
- ./unifi-os-server/data:/data
- ./unifi-os-server/srv:/srv
- ./unifi-os-server/var-lib-unifi:/var/lib/unifi
- ./unifi-os-server/var-lib-mongodb:/var/lib/mongodb
- ./unifi-os-server/etc-rabbitmq-ssl:/etc/rabbitmq/ssl
ports:
- 11443:443
- 5005:5005 # Optional
- 9543:9543 # Optional
- 6789:6789 # Optional
- 8080:8080
- 8443:8443 # Optional
- 8444:8444 # Optional
- 3478:3478/udp
- 5514:5514/udp # Optional
- 10003:10003/udp
- 11084:11084 # Optional
- 5671:5671 # Optional
- 8880:8880 # Optional
- 8881:8881 # Optional
- 8882:8882 # Optional
restart: unless-stopped
networks: {}
The container says “running”, but no GUI is available at http://mytruenasIP:11443, which is where it’s supposed to be ![]()
Is a possible issue that the container uses “privileged: true”, since as per the GitHub readme:
“The underlying structure of UniFi OS Server runs every component as systemd services which requires access to the host cgroup.”
EDIT: I’m a fool. The above is working fine, but it’s “https://….:11443” ![]()