[BUG] Binaries are not installed (on EOL kernels synology + other?) #306
Comments
|
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
|
A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue. |
|
Post full logs, starting before our ascii logo. |
|
I can't replicate it: #305 (comment) |
|
I suspect this is the 3.x kernel / qt6 ABI issue and as such there's no real solution for it. |
|
I am also seeing this happen on 4.4.302+ on a synology ( Re-running between both containers, the md5 for libQt6Core.so.6 is the same |
|
I'm also seeing this on Leading to a 404 when downloading a book, and this in the log: |
|
And here's a full log as requested earlier in the thread: calibre-web-log.txt |
|
Hello, Installation done using portainer and docker-compose file Logs are here : logs calibre-web.txt |
|
I hate to be that guy, but we're not going to spend time troubleshooting issues on kernels that have been end of life for over 2 years (referring to the 4.4 kernel crowd in here, the 3.2 kernel has been EOL for 6 years). My suggestion is that you revert to an older version until you find one that works and pin it, harass your hardware manufacturer to provide reasonable updates to their software, or find a container that caters to out of date systems like this. To be clear, some of our containers will work fine on out of date end of life stuff, some won't, it's not something we go out of our way to make happen, though with that said, if there is a way to support these old kernels without negatively impacting other users, we would definitely look at a user provided PR. |
|
@drizuid understood. should I close the issue? |
|
Let's see if @thespad has any thoughts first, he's more knowledgeable about these issues than I am. |
|
I have the same issue in Synology. I even rollbacked to 0.6.21-ls274 but I got the same problem. Binaries are not available in container. I think that it could be due to some recent Ubuntu updates, because my previous 0.6.22 container was working fine one week ago until I updated to 0.6.23 tag. |
without you posting a kernel version that isn't older than 4.19, there is nothing for us to help you with. If your kernel is older than 4.19, you need to try older versions until it works, restore a backup, or ask your vendor to resolve the kernel issue. I am now assuming the binaries being discussed are from the docker mod though, you can look through https://hub.docker.com/r/linuxserver/mods/tags?page_size=&ordering=&name=universal-calibre and find a version of the mob predating the rebase. Perhaps |
My current kernel version is Linux synology 4.4.302+ #69057 SMP Fri Jan 12 17:02:28 CST 2024 x86_64 GNU/Linux synology_geminilake_920+. Synology DSM 7.2.1-69057 Update 5. I have no pending updates in my device. I will try another calibre-web release and docker mod version and report back. |
This is the issue, this kernel has been end of life for over 2 years, as applications are updated and their base os layers in containers are updated, things that haven't been supported in 2+ years are going to have issues. The best way to maintain support is to not upgrade unless you know it will work, if you don't know, run a NEW container under a new name and test, if it doesn't work, pin your version and never upgrade again (much like your vendor has done with your kernel) |
I'm not sure this is possible. This mod downloads the binaries from the calibre release assets and it appears only the latest release makes these available. |
|
I tried few older versions (for calibre web and for binaries) and it is not working. Is it possible somehow to add mod for legacy versions of kernel ? |
As @ianmetcalf said, This mod (what ever is the version of the mod) download the binaries from the calibre release assets in github and it appears only the latest release makes these available. So as a workaround, if you want to install an old version of the caliber binaries, you can use the "Custom Scripts" solution in caliber-web to install the dependencies and binaries with the desired version (mostly like it's done in the mod in fact). For synology, it should look like this:
Be careful of the End Of Line of the script on the synology, it should be Linux EOL (LF) and it is actually windows EOL (CR LF) in my txt attachment. You can choose the version of the calibre binaries by modifying |
|
The mod is versioned, you can just use an older tag from this list if you need an older version of the calibre binary itself. Note that this won't change the versions of the depedencies as they're installed at runtime. |
@thespad: As ianmetcalf said, this mod (what ever is the versioned version of the mod) download the binaries from the calibre release assets in github and it appears only the latest release makes the binaries available, for old version, only source code are available. |
|
@loli71 Which version do you use in your script ? I tried all to 7.6.0 and still no convert button |
|
i'm using the version that is in the script I posted: |
|
I tried both ideas but nothing is working still no convert button, On my Synology NAS which is using Linux 4.4.302+ |
|
Oh, right, we do the download at runtime because the binaries are huge. Apologies I had forgotten. Completely mad that they're stripping the release artifacts from old GH releases though. |
drizuid
changed the title
|
I have pinned this issue. This is not something linuxserver.io can or will fix. We expect our containers to be run on non-end-of-life hardware and while it may work sometimes, we do not put in any special effort to support outdated systems. At this point, with a solution provided above and this being out of scope for our support, I will prepare to close this in the next couple of days, but I will leave it pinned for reference. |
@cuksi : check your docker logs when you launch your container, you should be able to see if the calibre binaries are well downloaded and installed. You can also do exec bash into you container after up and running to check if you have symlinks for the binaries in /usr/bin/ |
It works like a charm! I used your script, only changed endlines to LF, and launched this compose.yaml file: Symlinks are correctly created. I'm now fixing my main calibre with this configuration. Thank you very much! |
|
I got this from log, I think something needs to be changed in script: @loli71 I entered usr/bin but I am not sure which files I need to find. |
|
@cuksi it seems that my script in attachment have windows carriage return instead of linux carriage return, this is what gpa090 explained when saying he replaced endlines (CR+LF) by LF. @gpa090 : you do not need anymore |
|
Can someone try |
|
@thespad I tired that before, if you changed something I will try. Just didn't understand did you upadted universal-calibre-v7.16.0 to contain all files? @loli71 I did what you sad for LF and now I got this log and it is stuck: EDIT: |
|
Yes
|
@loli71 solution from above work like charm! Only here is new script file with changed carriage return for Unix calibre.sh.txt @thespad It is working! Thank you for adding this! So this is second solution that is working. Just be patient download is bit slow probably because of server, for both solutions. Special thanks to @loli71 , @thespad and to @gpa090 for finding solutions! P.S. Guys if you ever come to Belgrade (Serbia) beer is on me! Thank you! |
|
Closing and locking this now to make it usable for anyone who stumbles across it. If you're getting issues with the mod on a 4.x kernel, use We can't give any assurances as to how long this version of Calibre will continue to work with the current version of Calibre-Web. |
Is there an existing issue for this?
Current Behavior
After trying to install
calibre-webusinglinuxserver/docker-calibre-webon Synology NAS via Container Manager, thecalibrebinaries are not being put into bin folder.They are not correctly built.
Probably related to #305.
Expected Behavior
No response
Steps To Reproduce
calibre-webusing Container Manager on Synology NAS.calibre-webdoes not have binaries installed trying to use calibre-web.Environment
CPU architecture
x86-64
Docker creation
docker-compose.yml --- services: calibre-web: image: lscr.io/linuxserver/calibre-web:latest container_name: calibre-web environment: - PUID=1000 - PGID=1000 - TZ=Etc/UTC - DOCKER_MODS=linuxserver/mods:universal-calibre #optional - OAUTHLIB_RELAX_TOKEN_SCOPE=1 #optional volumes: - /volume1/docker/calibre-web/config:/config - /volume1/docker/calibre-web/library:/books ports: - 8083:8083 restart: unless-stoppedContainer logs
The text was updated successfully, but these errors were encountered: