Help and support for Linux users.

[Docker] Error importing comics - Error retrieving

LainX84
Topic Author
Offline
New Member

8 months 1 week ago #9915 by LainX84

[Docker] Error importing comics - Error retrieving was created by LainX84

Hello,

I am experiencing issues with my current YACReaderLibraryServer configuration on Docker.
These issues arose after replacing my NAS (from Qnap to Ugreen).
The connection between the NAS and the Linux machine is via NFS v3.
Mounts are configured as follows:

# Mount NFS
192.168.0.2:/volume1/Fumetteria/Manga /share/ugreen/yacreaderlibraryserver/comics/Manga nfs _netdev,noatime,async,nfsvers=3,tcp,rsize=1048576,wsize=1048576 0 0
192.168.0.2:/volume1/Fumetteria/Manhua /share/ugreen/yacreaderlibraryserver/comics/Manhua nfs _netdev,noatime,async,nfsvers=3,tcp,rsize=1048576,wsize=1048576 0 0
192.168.0.2:/volume1/Fumetteria/Manhwa /share/ugreen/yacreaderlibraryserver/comics/Manhwa nfs _netdev,noatime,async,nfsvers=3,tcp,rsize=1048576,wsize=1048576 0 0
192.168.0.2:/volume1/Fumetteria/Manhwa-to-Manga /share/ugreen/yacreaderlibraryserver/comics/Manhwa-to-Manga nfs _netdev,noatime,async,nfsvers=3,tcp,rsize=1048576,wsize=1048576 0 0
192.168.0.2:/volume1/Fumetteria/ArtBook /share/ugreen/yacreaderlibraryserver/comics/ArtBook nfs _netdev,noatime,async,nfsvers=3,tcp,rsize=1048576,wsize=1048576 0 0

I completely recreated (with a new database) the Docker version following these commands:

Code:

mkdir -p /home/matteo/YACReaderLibraryServer/{conf,db}

docker run -d \
  --name=YACReaderLibraryServer \
  -e PUID=1000 \
  -e PGID=10 \
  -e TZ=Europe/Rome \
  -p 9999:8080 \
  -v /home/matteo/YACReaderLibraryServer/conf:/config \
  -v /home/matteo/YACReaderLibraryServer/db:/comics/.yacreaderlibrary \
  -v /share/ugreen/yacreaderlibraryserver/comics/ArtBook:/comics/ArtBook \
  -v /share/ugreen/yacreaderlibraryserver/comics/Manga:/comics/Manga \
  -v /share/ugreen/yacreaderlibraryserver/comics/Manhua:/comics/Manhua \
  -v /share/ugreen/yacreaderlibraryserver/comics/Manhwa:/comics/Manhwa \
  -v /share/ugreen/yacreaderlibraryserver/comics/Manhwa-to-Manga:/comics/Manhwa-to-Manga \
  --restart unless-stopped \
  yacreader/yacreaderlibraryserver:latest

By doing so, the .yacreaderlibrary folder is located on the host, as are the configuration files, while the cbz files are on the NAS (with mechanical disks).

The service starts and I have successfully created the library and the service has started normally.

root@61c17d65dbfa:/# YACReaderLibraryServer list-libraries
Comics Library : /comics

From the logs, I see the following messages (I excluded the QR code):

Code:

matteo@docker-server:~/YACReaderLibraryServer/conf/.local/share/YACReader/YACReaderLibrary$ cat yacreaderlibrary.log
INFO  2026-01-28T01:09:04.966 YACReaderLibraryServer attempting to start
INFO  2026-01-28T01:09:04.966 ---------- System & configuration ----------
INFO  2026-01-28T01:09:04.974 "SYSTEM INFORMATION"
INFO  2026-01-28T01:09:04.974 "Qt version: 6.4.2"
INFO  2026-01-28T01:09:04.974 "Build ABI: x86_64-little_endian-lp64"
INFO  2026-01-28T01:09:04.974 "build CPU architecture: x86_64"
INFO  2026-01-28T01:09:04.974 "CPU architecture: x86_64"
INFO  2026-01-28T01:09:04.974 "Kernel type: linux"
INFO  2026-01-28T01:09:04.974 "Kernel version: 6.8.0-90-generic"
INFO  2026-01-28T01:09:04.974 "Product info: Ubuntu 24.04.3 LTS"
INFO  2026-01-28T01:09:04.974 ""
INFO  2026-01-28T01:09:04.974 "APP INFORMATION"
INFO  2026-01-28T01:09:04.974 "Image formats supported: bmp, cur, gif, icns, ico, jpeg, jpg, mng, pbm, pgm, png, ppm, tga, tif, tiff, wbmp, webp, xbm, xpm"
INFO  2026-01-28T01:09:04.974 "SQLite driver available: yes"
INFO  2026-01-28T01:09:04.974 "Compression backend: 7zip"
INFO  2026-01-28T01:09:04.974 "PDF support: Poppler"
INFO  2026-01-28T01:09:04.974 ""
INFO  2026-01-28T01:09:04.974 Libraries:
INFO  2026-01-28T01:09:04.974 --------------------------------------------
INFO  2026-01-28T01:09:04.975 YACReaderLibrary starting
INFO  2026-01-28T01:09:04.975 Running on "172.17.0.7:8080"
WARN  2026-01-28T01:09:14.079 QObject: Cannot create children for a parent that is in a different thread.
(Parent is RequestMapper(0x63a374301540), parent's thread is QThread(0x63a3742fb2a0), current thread is QThread(0x63a374302730)
WARN  2026-01-28T01:57:10.870 HttpRequest: received broken HTTP request, invalid first line
WARN  2026-01-28T01:57:11.069 HttpRequest: received broken HTTP request, invalid first line
WARN  2026-01-28T02:10:07.824 HttpRequest: received broken HTTP request, invalid first line
WARN  2026-01-28T02:10:07.935 HttpRequest: received broken HTTP request, invalid first line
WARN  2026-01-28T03:11:11.294 HttpRequest: received broken HTTP request, invalid first line
WARN  2026-01-28T03:11:11.454 HttpRequest: received broken HTTP request, invalid first line
WARN  2026-01-28T03:18:55.781 HttpRequest: received broken HTTP request, invalid first line
WARN  2026-01-28T03:18:55.890 HttpRequest: received broken HTTP request, invalid first line
WARN  2026-01-28T04:34:24.152 HttpRequest: received broken HTTP request, invalid first line
WARN  2026-01-28T04:34:24.329 HttpRequest: received broken HTTP request, invalid first line
WARN  2026-01-28T04:52:15.665 HttpRequest: received broken HTTP request, invalid first line
WARN  2026-01-28T04:52:15.779 HttpRequest: received broken HTTP request, invalid first line
WARN  2026-01-28T05:16:04.774 HttpRequest: received broken HTTP request, invalid first line
WARN  2026-01-28T05:16:04.960 HttpRequest: received broken HTTP request, invalid first line
WARN  2026-01-28T05:35:28.609 HttpRequest: received broken HTTP request, invalid first line
WARN  2026-01-28T05:36:10.258 HttpRequest: received broken HTTP request, invalid first line
WARN  2026-01-28T05:36:10.369 HttpRequest: received broken HTTP request, invalid first line
WARN  2026-01-28T08:39:30.361 Template: missing variable {page} in folder
WARN  2026-01-28T08:39:30.361 Template: missing variable {pages} in folder
WARN  2026-01-28T08:39:33.456 Template: missing variable {page} in folder
WARN  2026-01-28T08:39:33.456 Template: missing variable {pages} in folder
WARN  2026-01-28T08:39:34.662 Template: missing variable {page} in folder
WARN  2026-01-28T08:39:34.663 Template: missing variable {pages} in folder
WARN  2026-01-28T08:39:35.179 Template: missing variable {page} in folder
WARN  2026-01-28T08:39:35.179 Template: missing variable {pages} in folder
WARN  2026-01-28T08:39:35.869 Template: missing variable {page} in folder
WARN  2026-01-28T08:39:35.869 Template: missing variable {pages} in folder
WARN  2026-01-28T08:46:18.212 QObject: Cannot create children for a parent that is in a different thread.
(Parent is RequestMapper(0x63a374301540), parent's thread is QThread(0x63a3742fb2a0), current thread is QThread(0x63a374302b90)
WARN  2026-01-28T08:47:42.660 QObject: Cannot create children for a parent that is in a different thread.
(Parent is RequestMapper(0x63a374301540), parent's thread is QThread(0x63a3742fb2a0), current thread is QThread(0x63a374302b90)
WARN  2026-01-28T08:48:21.045 QObject: Cannot create children for a parent that is in a different thread.
(Parent is RequestMapper(0x63a374301540), parent's thread is QThread(0x63a3742fb2a0), current thread is QThread(0x63a374302b90)
WARN  2026-01-28T11:14:11.059 QObject: Cannot create children for a parent that is in a different thread.
(Parent is RequestMapper(0x63a374301540), parent's thread is QThread(0x63a3742fb2a0), current thread is QThread(0x63a374306970)
WARN  2026-01-28T11:14:38.871 QObject: Cannot create children for a parent that is in a different thread.
(Parent is RequestMapper(0x63a374301540), parent's thread is QThread(0x63a3742fb2a0), current thread is QThread(0x63a374302b90)
WARN  2026-01-28T11:16:23.588 QObject: Cannot create children for a parent that is in a different thread.
(Parent is RequestMapper(0x63a374301540), parent's thread is QThread(0x63a3742fb2a0), current thread is QThread(0x63a374302b90)
WARN  2026-01-28T11:16:26.926 QObject: Cannot create children for a parent that is in a different thread.
(Parent is RequestMapper(0x63a374301540), parent's thread is QThread(0x63a3742fb2a0), current thread is QThread(0x63a3743057b0)

Please Log in or Create an account to join the conversation.

Luis Ángel
Offline
Administrator

8 months 1 week ago #9916 by Luis Ángel

Replied by Luis Ángel on topic [Docker] Error importing comics - Error retrieving

Check the log output after restarting the container, you’ll see some output about library validation, let’s see if the app catches anything.

Contribute to the project becoming a patron: www.patreon.com/yacreader
You can also donate via Pay-Pal: www.paypal.com/donate?business=5TAMNQCDD...e=Support+YACReader\

Please Log in or Create an account to join the conversation.

LainX84
Topic Author
Offline
New Member

8 months 1 week ago #9920 by LainX84

Replied by LainX84 on topic [Docker] Error importing comics - Error retrieving

Container restarted.
Starting import.
After few item, same error.
From the log (just the last row) :

Code:

Connection to localhost (::1) 8080 port [tcp/*] succeeded!
[ls.io-init] done.
WARN  2026-01-28T15:44:37.102 QObject: Cannot create children for a parent that is in a different thread.
(Parent is RequestMapper(0x5dbc56e207f0), parent's thread is QThread(0x5dbc56e132a0), current thread is QThread(0x5dbc56e1d5f0)

Nothing other...

Please Log in or Create an account to join the conversation.

kingrobt
Offline
New Member

7 months 2 weeks ago #9961 by kingrobt

Replied by kingrobt on topic [Docker] Error importing comics - Error retrieving

Your Docker setup actually looks fine, and since the server starts and creates the library without errors, this doesn’t look like a YACReader issue. It’s very likely related to the NFS change when you moved from QNAP to Ugreen. The first thing I would check is permissions from inside the container. Exec into it and try listing the folders and creating a test file inside one of the /comics directories. If you can’t create a file, then it’s a permission mapping issue on the NFS share. Ugreen may be handling NFS exports differently than QNAP, especially with squash settings. If “all squash” is enabled or users are being mapped to nobody, your container user (PUID 1000 / PGID 10) might not actually have proper write access. Another thing to consider is file locking. Since YACReader uses SQLite, NFS v3 can sometimes cause locking problems. Adding nolock to your mount options or switching to NFS v4 (if supported) often fixes strange behavior with apps that rely on databases. Given that there are no obvious errors in your logs, I’d start with checking write access inside the container. That usually reveals the issue pretty quickly after an NAS migration.

Please Log in or Create an account to join the conversation.

Moderators: Luis Ángel

[Docker] Error importing comics - Error retrieving

Thanks for downloading YACReader!

YACReader for iOS and Android

Support YACReader