Universal-Calibre mod fails to initiailse

[shikasta-net]

This was working until I restarted Docker a few weeks ago and have only just noticed this service was unavailable since then (yes, I need better monitoring).

• linuxserver/calibre-web:0.6.18 (0.6.19 fails to start for other reasons)
• linuxserver/mods:universal-calibre-v6.8.0
• Docker 17.12.1
• docker-compose 1.29.2
• Ubuntu 18.04

After the usual install information I get

Processing triggers for libc-bin (2.31-0ubuntu9.7) ...
[mod-init] Attempting to run Docker Modification Logic
[mod-init] Applying linuxserver/mods:universal-calibre-v6.8.0 files to container
[mod-init] linuxserver/mods:universal-calibre-v6.8.0 applied to container
s6-rc-compile: fatal: unable to read /etc/s6-overlay/s6-rc.d/init-mods-end/type: No such file or directory

and the service never starts (although the container is still running).
If I switch back to linuxserver/calibre-web:calibre-v5.9.0-ls1, it starts.

[github-actions]

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

[shikasta-net]

Coming back to this after some updates. Same problem more/different information from the logs. I suspect my original issue was some version mismatch that lead to me trying to pin the version of universal-calibre, and subsequently meant it didn't work.

• linuxserver/calibre-web:0.6.19
• Docker 20.10.12
• docker-compose 1.29.2
• Ubuntu 20.04.5

mod universal-calibre-v6.0.0 is ok
mod universal-calibre-v6.1.0 and 6.2.0 fail during startup with:

Processing triggers for libc-bin (2.35-0ubuntu3.1) ...#015
**** Fetching calibre bin ****
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current        Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100     9  100     9    0     0     16      0 --:--:-- --:--:-- --:--:--    16
tar: This does not look like a tar archive
xz: (stdin): File format not recognized
tar: Child returned status 1
tar: Error is not recoverable: exiting now
/etc/cont-init.d/98-calibre: line 89: /app/calibre/calibre_postinstall: No such file or directory
cont-init: info: /etc/cont-init.d/98-calibre exited 127

mod universal-calibre-v6.3.0 to v6.16.0 fails during startup with:

Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
**** Installing/updating calibre ****
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current  Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100     9  100     9    0     0     20      0 --:--:-- --:--:-- --:--:--    20
tar: This does not look like a tar archive
xz: (stdin): File format not recognized
tar: Child returned status 1
tar: Error is not recoverable: exiting now
/etc/s6-overlay/s6-rc.d/init-mod-universal-calibre-setup/run: line 59: /app/calibre/calibre_postinstall: No such file or directory

mod universal-calibre-v6.17.0 starts ok
This made it easier to find the actual problem, which is that

CALIBRE_RELEASE="$(cat /CALIBRE_RELEASE)"
curl -o /tmp/calibre.txz -L "https://github.com/kovidgoyal/calibre/releases/download/${CALIBRE_RELEASE}/calibre-${CALIBRE_RELEASE:1}-x86_64.txz"

returns "Not Found" to the output file (not a tar) for releases other than 6.0.0 and latest. I'm not sure if it should expect them to be available but because they aren't, expecting the package to match the requested image name, makes it unreliable for anything other than the most recent. It would be useful changing this to

curl -f -o /tmp/calibre.txz -L "https://github.com/kovidgoyal/calibre/releases/download/${CALIBRE_RELEASE}/calibre-${CALIBRE_RELEASE:1}-x86_64.txz"
if [ "$?" == "0" ]; then
   ...

so it's more obvious in the future if you're using a version for which the artifact is gone.

[github-actions]

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

[github-actions]

This issue is locked due to inactivity