Closed barthoefs closed 2 years ago
Remove the apk
commands from the startup script (or delete it entirely) and see if that helps.
Remove the
apk
commands from the startup script (or delete it entirely) and see if that helps.
Hi. I just did that as the file seems to be from 2019... Renamed to _old and homebridge started without issues. Thanks for the support!
Great, errors in that script shouldn't stop it from running, I'll see what's going on.
Great, errors in that script shouldn't stop it from running, I'll see what's going on.
You can find my "defective" below. Error was on line 17?
#!/bin/sh
#
# Docker Homebridge Custom Startup Script - oznu/homebridge
#
# This script can be used to customise the environment and will be executed as
# the root user each time the container starts.
#
# If using this to install plugins DO NOT use the global flag (-g).
#
# Example installing homebridge plugin:
#
# npm install homebridge-hue
#
# Example installing packages using default image (Alpine Linux):
#
apk add --no-cache ffmpeg ffmpeg-libs libpcap-dev
#
# If you're running a debian based version of this container please use apt-get to install packages.
#
It was the "apk" command. The image swapped from Apline based to Ubuntu based so "apk" is no longer present.
https://github.com/oznu/docker-homebridge/issues/437
ffmpeg is now bundled with the image so it's redundant anyway.
Errors in the startup.sh
script will no longer prevent Homebridge from starting as of the latest image.
Hi @oznu I also experienced some issue with latest update which could be related. After upgrading (tried both WatchTower and Manually) it losses all plugins, I received the below error messages: No plugin was found for the platform "Yeelighter" in your config.json. Please make sure the corresponding plugin is installed correctly. In the node_modules only homebridge and homebridge-config-ui-x exist. Tried to install again from UI without luck, it just hangs:
USER: homebridge DIR: /var/lib/homebridge CMD: pnpm install --save homebridge-harmony@latest
Progress: resolved 80, reused 21, downloaded 0, added 0 The authenticity of host 'github.com (140.82.121.3)' can't be established. ECDSA key fingerprint is SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyProgress: resolvedProgress: resolved 775, reused 775, downloaded 0, added 0gerprint])?
@maisun - please create a new issue. include the full contents of the package.json
.
@oznu : sorry will create a new issue
@maisun - please create a new issue. include the full contents of the
package.json
.
New issue created, please let me know any info is missing, many thanks in advance!
Describe The Bug
After automatic watchtower upgrade this morning (fetching the latest docker image) the container fails to start up properly. Until yesterday I had no issues (my logs are attached).
Don't know if this is the issue:![image](https://user-images.githubusercontent.com/89918293/174010269-4b31ed6f-9f55-4b61-b433-9f30dd86cd24.png)
Docker Config
Logs
Host Operating System
Synology DSM
Host Architecture
x86_64 / amd64