[Bug]: latest docker update (today 2023-11-03) updated with Watchtower breaks all

[imc67]

Controller Version

v5.12.7

Describe the Bug

since more than a year all updates with Watchtower and your great docker image worked fine ... until today. After update no switches, api's, clients connected. Lot's of info in the log but I can't make anything of it.

Expected Behavior

smoothless update and a working container

Steps to Reproduce

update to :latest

How You're Launching the Container

version: "3.1"

services:
  omada-controller:
    container_name: omada-controller
    image: mbentley/omada-controller:latest
    restart: unless-stopped
    stop_grace_period: 60s
    network_mode: host
    environment:
      - PUID=508
      - PGID=508
      - MANAGE_HTTP_PORT=8088
      - MANAGE_HTTPS_PORT=8043
      - PORTAL_HTTP_PORT=8088
      - PORTAL_HTTPS_PORT=8843
      - PORT_APP_DISCOVERY=27001
      - PORT_ADOPT_V1=29812
      - PORT_UPGRADE_V1=29813
      - PORT_MANAGER_V1=29811
      - PORT_MANAGER_V2=29814
      - PORT_DISCOVERY=29810
      - SHOW_SERVER_LOGS=true
      - SHOW_MONGODB_LOGS=false
      - SSL_CERT_NAME=tls.crt
      - SSL_KEY_NAME=tls.key
      - TZ=Etc/UTC
    volumes:
      - ./appdata/data:/opt/tplink/EAPController/data
      - ./appdata/logs:/opt/tplink/EAPController/logs
      - ./appdata/work:/opt/tplink/EAPController/work

Container Logs

2023-11-03T17:37:50.523946878Z 11-03-2023 17:37:50.521 INFO [server-comm-pool-1] [] c.t.s.e.s.c.h.EcspV2DeviceContextHelper(): close device 34-60-F9-2C-BD-0A channel /192.168.67.2:29814 -> /192.168.67.30:39623, cause not match pre connect status

or 

2023-11-03T17:37:50.523030684Z 11-03-2023 17:37:50.521 WARN [server-comm-pool-1] [] c.t.s.e.s.c.c(): get device adopt info for 34-60-F9-2C-BD-0A error when handle new pre connect, exception: 
2023-11-03T17:37:50.523117869Z java.lang.NullPointerException: username is marked non-null but is null

MongoDB Logs

No response

Additional Context

No response

[johnpierson]

It looks like @mbentley is looking at this now. #365 (comment)

[mbentley]

This will be fixed by #367. Temporary workaround is to add an env var as seen here:
#365 (comment)