Closed acahir closed 1 year ago
You are not running the latest image. After pulling a new image, you need to delete and recreate the container.
the latest image is up to date.
Mostly an FYI. Blew away the container, removed and reinstalled the Homebridge Synology package. Recreated the container and that seems to have cleared away whatever was stuck. Version of config-UI is up to date to start, vs being very old.
Strangely, on the docker image command line, node isn't anywhere to be found now? Is it no longer required?
You are not running the latest image. After pulling a new image, you need to delete and recreate the container.
the latest image is up to date.
I had "Reset" the container in the Docker Synology app, which I believe is the new term used in DSM7
Describe The Bug
Similar to #467, I upgraded homebridge-config-ui plugin, and then the webUI was refusing to start with the following error in the logs:
Checking into it, seems older version of node don't support the ?? operator. Sure enough, node in this docker container is v12:
The docker container is up to date, updated both via pulling latest from the registry and by using the Synology package. I've had the docker image set up since 2019, so it seems that the node version isn't being updated from when the container was first created.
Per #467, attempted to update node:
Have already pulled down the latest version a week or so ago when I first tried to upgrade the config-ui plugin and ran into the same problem.
Docker Config
Logs
No response
Host Operating System
Synology DSM 7
Host Architecture
x86_64 / amd64