Application
lidarr
Host platform
Synology and probably every alpine-based lidarr docker image?
Script
lidarr/setup.bash
Script Version
1.4.5
Describe the bug
setup.bash installs two xq binaries:
- xq via apk — sibprogrammer's XML pretty-printer (lands at /usr/bin/xq)
- yq via uv pip install — python-yq, which also provides xq as an XML→JSON converter
The apk version at /usr/bin/xq takes PATH priority over the pip version. When functions.bash runs:
arrApiKey="$(cat /config/config.xml | xq | jq -r .Config.ApiKey)"
It gets the sibprogrammer xq, which outputs formatted XML instead of JSON. jq fails with Invalid numeric literal, arrApiKey is empty, and every script loops forever: is not ready, sleeping until valid response...
Environment
- Image: ghcr.io/linuxserver/lidarr (Alpine-based)
- xq version installed by apk: 1.3.0 (sibprogrammer)
- python-yq xq: not installed (xq binary is never placed in PATH)
To Reproduce
Install lidarr on synology and lidarr-extended.
Expected behavior
Processed imports.
Probable fix: remove xq from installs under setup.bash
NOTE
Your request will not be addressed without proper detail and logs. Always make sure you have updated to the latest script versions before opening an issue or your issue will not be reviewed.
Application
lidarr
Host platform
Synology and probably every alpine-based lidarr docker image?
Script
lidarr/setup.bash
Script Version
1.4.5
Describe the bug
setup.bash installs two xq binaries:
The apk version at /usr/bin/xq takes PATH priority over the pip version. When functions.bash runs:
arrApiKey="$(cat /config/config.xml | xq | jq -r .Config.ApiKey)"
It gets the sibprogrammer xq, which outputs formatted XML instead of JSON. jq fails with Invalid numeric literal, arrApiKey is empty, and every script loops forever: is not ready, sleeping until valid response...
Environment
To Reproduce
Install lidarr on synology and lidarr-extended.
Expected behavior
Processed imports.
Probable fix: remove xq from installs under setup.bash
NOTE
Your request will not be addressed without proper detail and logs. Always make sure you have updated to the latest script versions before opening an issue or your issue will not be reviewed.