Infrastructure/docker/omada-controller/docker-compose.yml

45 lines
1.4 KiB
YAML

services:
omada-controller:
container_name: omada-controller
# Pin major.minor — never use `latest`, a version bump can break the Mongo schema mid-upgrade.
# Check https://hub.docker.com/r/mbentley/omada-controller/tags for the current recommended tag.
image: mbentley/omada-controller:6.3
restart: unless-stopped
ulimits:
nofile:
soft: 4096
hard: 8192
stop_grace_period: 60s
# Host networking: Omada device discovery/adoption relies on broadcast + a wide range of
# UDP/TCP ports below. Simplest to just share the desktop's network stack directly.
network_mode: host
environment:
- PUID=508
- PGID=508
- TZ=Europe/Vienna
- MANAGE_HTTP_PORT=8088
- MANAGE_HTTPS_PORT=8043
- PORTAL_HTTP_PORT=8088
- PORTAL_HTTPS_PORT=8843
- UPGRADE_HTTPS_PORT=8044
- PORT_APP_DISCOVERY=27001
- PORT_DISCOVERY=29810
- PORT_MANAGER_V1=29811
- PORT_ADOPT_V1=29812
- PORT_UPGRADE_V1=29813
- PORT_MANAGER_V2=29814
- PORT_TRANSFER_V2=29815
- PORT_RTTY=29816
- PORT_DEVICE_MONITOR=29817
- WEB_CONFIG_OVERRIDE=false
- SHOW_SERVER_LOGS=true
- SHOW_MONGODB_LOGS=false
- SSL_CERT_NAME=tls.crt
- SSL_KEY_NAME=tls.key
volumes:
- omada-data:/opt/tplink/EAPController/data
- omada-logs:/opt/tplink/EAPController/logs
volumes:
omada-data:
omada-logs: