Omada-Controller Docker-Compose

das Netzwerk docker_subnet muss angelegt sein oder an eigene Umgebung angepasst werden, oder die Zeilen Networks entfernen für Default

Volume ist ein Host bind

Docker-Compose

services:
  omada-controller:
    container_name: omada
    hostname: omada
    image: mbentley/omada-controller:latest-chromium-amd64
    restart: always
    security_opt:
      - no-new-privileges:true
    ulimits:
      nofile:
        soft: 4096
        hard: 8192
    stop_grace_period: 60s
    environment:
      # - PUID='508'
      # - PGID='508'
      - MANAGE_HTTP_PORT=8088
      - MANAGE_HTTPS_PORT=8043
      - PORTAL_HTTP_PORT=8088
      - PORTAL_HTTPS_PORT=8843
      - PORT_ADOPT_V1=29812
      - PORT_APP_DISCOVERY=27001
      - PORT_DISCOVERY=29810
      - PORT_MANAGER_V1=29811
      - PORT_MANAGER_V2=29814
      - PORT_TRANSFER_V2=29815
      - PORT_RTTY=29816
      - PORT_UPGRADE_V1=29813
      - SHOW_SERVER_LOGS=true
      - SHOW_MONGODB_LOGS=false
      - SSL_CERT_NAME='tls.crt'
      - SSL_KEY_NAME='tls.key'
      - TZ=Europe/Berlin
    ports:
      - '8089:8088'
      - '8043:8043'
      - '8843:8843'
      - '27001:27001/udp'
      - '29810:29810/udp'
      - '29811-29816:29811-29816'
    volumes:
      - /docker_data/omada/data:/opt/tplink/EAPController/data
      - /docker_data/omada/logs:/opt/tplink/EAPController/logs
    networks:
      docker_subnet:
        ipv4_address: 172.18.0.15

networks:
  docker_subnet:
    external: true