Docker package 1.0.32 still shows version 1.5.0 in the logs and show upgrade to 1.5.1 available in GUI.

[ekobres]

Describe The Bug

Latest docker image (1.0.32) still claims to be version 1.5.0 Portainer shows ENV:

DSM_HOSTNAME | DS519Plus
-- | --
ENABLE_AVAHI | 1
HOME | /home/homebridge
HOMEBRIDGE_APT_PACKAGE | 1
HOMEBRIDGE_PKG_VERSION | 1.0.32
npm_config_prefix | /opt/homebridge
PATH | /opt/homebridge/bin:/var/lib/homebridge/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
S6_CMD_WAIT_FOR_SERVICES_MAXTIME | 0
S6_KEEP_ENV | 1
S6_OVERLAY_VERSION | 3.1.1.2
UIX_CUSTOM_PLUGIN_PATH | /var/lib/homebridge/node_modules

Docker Config

docker run -d --name=homebridge \
-e DSM_HOSTNAME=DS519Plus \
-v /volume1/docker/homebridge:/homebridge \
--net=host \
--restart always \
oznu/homebridge:latest

Logs

[11/23/2022, 2:48:39 PM] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null
[11/23/2022, 2:50:05 PM] [HB Supervisor] OS: Linux 4.4.180+ x64
[11/23/2022, 2:50:05 PM] [HB Supervisor] Node.js v18.12.1 /opt/homebridge/bin/node
[11/23/2022, 2:50:05 PM] [HB Supervisor] Homebridge Path: /var/lib/homebridge/node_modules/homebridge/bin/homebridge
[11/23/2022, 2:50:05 PM] [HB Supervisor] UI Path: /opt/homebridge/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
[11/23/2022, 2:50:08 PM] [Homebridge UI] Homebridge Config UI X v4.50.2 is listening on :: port 8581
[11/23/2022, 2:50:08 PM] [HB Supervisor] Starting Homebridge with extra flags: -P /var/lib/homebridge/node_modules --strict-plugin-resolution
[11/23/2022, 2:50:08 PM] [HB Supervisor] Started Homebridge v1.5.0 with PID: 147

Host Operating System

Other (specify in description)

Host Architecture

x86_64 / amd64

[realdannys]

Doing the same with 1.60 now - I was assuming the container version just hasn't updated to 1.5.1 or 1.6.0 yet as there's nothing in the release logs to say it has.

[tosate]

The package needs to be available before a new image can be published.

[tosate]

I have started the container with a clean data directory that gets mapped to /homebridge. After this, it run with version 1.6.0:

[1/22/2023, 7:20:13 PM] [HB Supervisor] Homebridge Config Path: /var/lib/homebridge/config.json
[1/22/2023, 7:20:13 PM] [HB Supervisor] Logging to /var/lib/homebridge/homebridge.log
[1/22/2023, 7:20:13 PM] [HB Supervisor] OS: Linux 5.15.32-v7+ arm
[1/22/2023, 7:20:13 PM] [HB Supervisor] Node.js v18.13.0 /opt/homebridge/bin/node
[1/22/2023, 7:20:13 PM] [HB Supervisor] Homebridge Path: /var/lib/homebridge/node_modules/homebridge/bin/homebridge
[1/22/2023, 7:20:13 PM] [HB Supervisor] UI Path: /opt/homebridge/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
[1/22/2023, 7:20:30 PM] [Homebridge UI] Homebridge Config UI X v4.50.2 is listening on :: port 8180
[1/22/2023, 7:20:31 PM] [HB Supervisor] Starting Homebridge with extra flags: -I -P /var/lib/homebridge/node_modules --strict-plugin-resolution
[1/22/2023, 7:20:31 PM] [HB Supervisor] Started Homebridge v1.6.0 with PID: 159

So, something had to be wrong with the data outside the container. I have found the file package.json with the content:

{
  "private": true,
  "description": "This file keeps track of which plugins should be installed.",
  "dependencies": {
    "homebridge": "^1.5.0",
    "homebridge-dummy": "^0.4.0",
    "homebridge-hue": "^0.13.51",
    "homebridge-knx": "^0.3.27",
    "homebridge-mqttthing": "^1.1.43"
  }
}

Seems like this prevented my node packages from being updated. After deleting this file, the container startup took about 9 minutes. Probably because a lot of stuff has been updated.

@oznu Thank you mate for your awesome work on this project! I am using it for years.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.