[Bug]: 5.13.30.8 won't start (older than last version executed) but LAST_RAN_OMADA_VER.txt doesn't exist

[jhgarrison]

Controller Version

No main screen or container logs to find this number

Describe the Bug

I initially pulled the "latest" tag but it won't start due to the dependency resolution issue documented elsewhere.

I deleted the container and the image, and pulled 5.13.30.8. Now the image refuses to start, with:

ERROR: The version from the image (5.13.30.8) is older than the last version executed (5.14.26.1)!  Refusing to start to prevent data loss!
  To bypass this check, remove /opt/tplink/EAPController/data/LAST_RAN_OMADA_VER.txt only if you REALLY know what you're doing!

However, /opt/tplink/EAPController/data/LAST_RAN_OMADA_VER.txt doesn't exist. In fact /opt/tplink/EAPController/ is empty.

I'm an experienced developer but Docker newbie.

Expected Behavior

Container starts up

Steps to Reproduce

As described above

How You're Launching the Container

$ sudo docker run --name omada-controller   --stop-timeout 60   --restart unless-stopped   --ulimit nofile=4096:8192   -p 8088:8088   -p 8043:8043   -p 8843:8843   -p 27001:27001/udp   -p 29810:29810/udp   -p 29811-29816:29811-29816   -e MANAGE_HTTP_PORT=8088   -e MANAGE_HTTPS_PORT=8043   -e PGID="508"   -e PORTAL_HTTP_PORT=8088   -e PORTAL_HTTPS_PORT=8843   -e PORT_ADOPT_V1=29812   -e PORT_APP_DISCOVERY=27001   -e PORT_DISCOVERY=29810   -e PORT_MANAGER_V1=29811   -e PORT_MANAGER_V2=29814   -e PORT_TRANSFER_V2=29815   -e PORT_RTTY=29816   -e PORT_UPGRADE_V1=29813   -e PUID="508"   -e SHOW_SERVER_LOGS=true   -e SHOW_MONGODB_LOGS=false   -e SSL_CERT_NAME="tls.crt"   -e SSL_KEY_NAME="tls.key"   -e TZ=Etc/UTC   -v omada-data:/opt/tplink/EAPController/data   -v omada-logs:/opt/tplink/EAPController/logs   mbentley/omada-controller:5.13

Container Logs

INFO: Validating user/group (omada:omada) exists with correct UID/GID (508:508)
INFO: Group (omada) doesn't exist; creating
INFO: User (omada) doesn't exist; creating
INFO: Time zone set to 'Etc/UTC'
INFO: Value of 'manage.http.port' already set to 8088 in omada.properties
INFO: Value of 'manage.https.port' already set to 8043 in omada.properties
INFO: Value of 'portal.http.port' already set to 8088 in omada.properties
INFO: Value of 'portal.https.port' already set to 8843 in omada.properties
INFO: Value of 'port.adopt.v1' already set to 29812 in omada.properties
INFO: Value of 'port.app.discovery' already set to 27001 in omada.properties
INFO: Value of 'port.upgrade.v1' already set to 29813 in omada.properties
INFO: Value of 'port.manager.v1' already set to 29811 in omada.properties
INFO: Value of 'port.manager.v2' already set to 29814 in omada.properties
INFO: Value of 'port.discovery' already set to 29810 in omada.properties
INFO: Value of 'port.transfer.v2' already set to 29815 in omada.properties
INFO: Value of 'port.rtty' already set to 29816 in omada.properties
INFO: Value of 'mongo.external' already set to false in omada.properties
INFO: Value of 'eap.mongod.uri' already set to mongodb://127.0.0.1:27217/omada in omada.properties
WARN: Ownership not set correctly on '/opt/tplink/EAPController/properties'; setting correct ownership (omada:omada)
ERROR: The version from the image (5.13.30.8) is older than the last version executed (5.14.26.1)!  Refusing to start to prevent data loss!
  To bypass this check, remove /opt/tplink/EAPController/data/LAST_RAN_OMADA_VER.txt only if you REALLY know what you're doing!

MongoDB Logs

[empty]

Additional Context

No response

[mbentley]

That path it is referring to is in your volume: omada-data. At some point, you had started, or attempted to start, version 5.14.26.1. I am not sure if you have an existing controller setup that exists in your persistent data or not. If you have not configured the controller and are wanting to start from scratch, you can remove the volumes docker volume rm omada-data, docker volume rm omada-logs and run the container again.

If you have configured the controller, then you need to remove the file in the volume. One way without finding where Docker is storing that directory on your host is to run a container with the data mounted and then start a shell so you can remove the file.

docker run -it --rm -v omada-data:/opt/tplink/EAPController/data -w /opt/tplink/EAPController/data alpine sh

From here, you should be able to list and remove the file.

[jhgarrison]

Ah, that was the missing part (persistent storage outside images), thank you. Still learning docker :-)