Upon pulling an updated version of the container, the container now gets stuck installing homebridge with dpkg.
Installing Homebridge...
Selecting previously unselected package homebridge.
(Reading database ... 35951 files and directories currently installed.)
Preparing to unpack /homebridge_1.0.24.deb ...
Running pre-install steps...
Unpacking may take several minutes on low powered devices.
Unpacking homebridge (1.0.24) ...
This will stay like this for over an hour (server is running a Ryzen 9, so I don't think we're a "low powered device" like a RPI)
I've tried going into the container and manually installing the package with dpkg but I've also gotten no luck as it too gets stuck (after killing the stuck process)
# ps -aux | grep "dpkg -i"
root 74 1.7 0.1 23472 21280 ? D 17:09 0:07 dpkg -i /homebridge_1.0.24.deb
# kill 74
# dpkg -i /homebridge_1.0.24.deb
(Reading database ... 35951 files and directories currently installed.)
Preparing to unpack /homebridge_1.0.24.deb ...
Running pre-upgrade steps...
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Unpacking may take several minutes on low powered devices.
Unpacking homebridge (1.0.24) over (1.0.24) ...
I've blasted away any mounted directories and started with a fresh container, but I still get the same issue, which leads me to believe that this may be an upstream problem.
$ docker logs -f homebridge
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service tzupdate: starting
s6-rc: info: service setup: starting
Thank you for using the oznu/homebridge docker image!
If you find this project useful please STAR it on GitHub:
https://github.com/oznu/docker-homebridge
Or donate to the project:
https://github.com/sponsors/oznu
https://paypal.me/oznu
s6-rc: info: service credits: starting
s6-rc: info: service credits successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service tzupdate successfully started
s6-rc: info: service legacy-cont-init successfully started
dpkg-query: no packages found matching homebridge
Installing Homebridge...
Selecting previously unselected package homebridge.
(Reading database ... 35951 files and directories currently installed.)
Preparing to unpack /homebridge_1.0.24.deb ...
Running pre-install steps...
Unpacking may take several minutes on low powered devices.
Unpacking homebridge (1.0.24) ...
^C
$ docker stop homebridge && docker rm homebridge
homebridge
$ docker-compose up -d
cgate-server is up-to-date
Creating homebridge ... done
$ docker logs -f homebridge
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service tzupdate: starting
s6-rc: info: service setup: starting
s6-rc: info: service credits: starting
Thank you for using the oznu/homebridge docker image!
If you find this project useful please STAR it on GitHub:
https://github.com/oznu/docker-homebridge
Or donate to the project:
https://github.com/sponsors/oznu
https://paypal.me/oznu
s6-rc: info: service credits successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service tzupdate successfully started
dpkg-query: no packages found matching homebridge
Installing Homebridge...
Selecting previously unselected package homebridge.
(Reading database ... 35951 files and directories currently installed.)
Preparing to unpack /homebridge_1.0.24.deb ...
Running pre-install steps...
Unpacking may take several minutes on low powered devices.
Unpacking homebridge (1.0.24) ...
Describe The Bug
Upon pulling an updated version of the container, the container now gets stuck installing homebridge with dpkg.
This will stay like this for over an hour (server is running a Ryzen 9, so I don't think we're a "low powered device" like a RPI)
I've tried going into the container and manually installing the package with dpkg but I've also gotten no luck as it too gets stuck (after killing the stuck process)
I've blasted away any mounted directories and started with a fresh container, but I still get the same issue, which leads me to believe that this may be an upstream problem.
Docker Config
Logs
Host Operating System
Ubuntu / Debian (or a variant)
Host Architecture
x86_64 / amd64