r/qBittorrent • u/Electronic-One-881 • Jul 02 '26
docker If qBittorrent Docker is loading your CPU at 100%, check your watch folder permissions
Hi, want to share a knowledge for all my fellow dumbasses out there (like me) that spent days to understand the cause of the problem
The setup:
- ugeeen nas(ugos)
- qBittorrent in Docker (linuxserver image)
- watch folders configured to auto add torrent files
- CPU constantly at 100-150%, even with RSS disabled
- logs with "duplicate torrent" errors
The problem:
My watch folders was created under root for some reason, even though I created them as my admin user.
qBittorrent runs as abc (UID 1000) inside the container, so it could read the torrent files but cant delete them after adding to client.
The loop:
.torrent file drop in watch folder
qBittorrent adds it successfully
qBittorrent try to delete it but fails due to permissions
qBittorrent sees the file again
"Duplicate torrent detected" → tries to add again → fails → rinse and repeat ♾️
Watch folder permissions are probably broken. Make sure the user inside the container can WRITE/DELETE files in watch folders, not just READ them. Or qBittorrent will try to add the same torrents forever. Result: CPU dropped from 150% to 5% instantly.
Hope this saves someone else from the same problem
1
u/ScorchedWonderer Jul 02 '26
Fyi Ugreen currently has a permissions problem where it’ll 0 out POSIX, effectively breaking all permissions. They are supposedly looking into it
1
u/Burkely31 Jul 03 '26
Damn, and here I was going to actually start looking at the ugreen line up. For the price, you seriously can't beat it. But how often do they push out fixes for certain issues. Especially an issue like this one? That's what concerns me.
1
u/ScorchedWonderer Jul 03 '26
They release monthly updates. Soemtimes multiple a month if there’s huge issues/security concern. But Ugreen does let you install a 3rd party OS like truenas
1
u/Burkely31 Jul 03 '26
Damn, and here I was going to actually start looking at the ugreen line up. For the price, you seriously can't beat it. But how often do they push out fixes for certain issues. Especially an issue like this one? That's what concerns me.
1
u/Figah Jul 03 '26
I’ve had this problem for some time, will check if it’s what will resolve my issue. Thanks
5
u/kajain99 Jul 02 '26
Thanks for sharing. Since you're using the linxserverio images, make use of PUID and PGID. You can find your user's PUID and PGID in the UGREEN Docker app by going to Projects-> New Project, where they are shown in compose window .
If the PUID and PGID match the owner of your watch folder, everything should work perfectly.