Replies: 13 comments
-
Not being particularly familiar with qbittorrent, there isn't much we can do here. If you can find more about the error, particularly what file it is complaining about being locked, we can at least identify if this is a Podman problem. |
Beta Was this translation helpful? Give feedback.
-
Ok, @mheon; I'll try to take a discussion w/ the guys @ linuxserver.io |
Beta Was this translation helpful? Give feedback.
-
This doesn't seem like a Windows specific issue, since the error seems to be Linux based. I would recommend removing the 'windows' label from this. |
Beta Was this translation helpful? Give feedback.
-
The label is auto-applied if the attached |
Beta Was this translation helpful? Give feedback.
-
Well so far no information has been provided that this is not a windows specific bug so I think the label should stay on. The command is being run on windows and it seems to be mounting windows directories, then QT complains about And running the provided command works just fine on my linux box so that would strongly suggest a problem with WSL maybe and IMO all WSL problems should be marked windows. |
Beta Was this translation helpful? Give feedback.
-
Fair enough! Could you run WSL logs? We could check for any WSL errors in there. Instructions to run WSL logs are here: https://aka.ms/wsllogs and please attach them to this thread and I can go through them. |
Beta Was this translation helpful? Give feedback.
-
@PIPOGit One other thing you can try is to to remove the -v options so the application wouldn't use the shared windows file system. Just thinking about it WSL uses 9p, right? Does 9p even support lock files, i.e. via flock() or fcntl() F_SETLK? |
Beta Was this translation helpful? Give feedback.
-
Well... Hi all! And thanks for the support! I'll try yo explain things. ;) The contextScript Execution, for logsI downloaded the script from: https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-wsl-logs.ps1 Original infoThe command is basically copied from here Windows ("host") folderWhere I run PODMAN "from":
First try: Without volumesScript
PowerShell OUTPUT
CONTAINER LOGS
Second try: With '
|
Beta Was this translation helpful? Give feedback.
-
Well... I think I've finally found out where the problem is. If I launch a container with the "
I guess there is a problem with the permissions for the " Thanks for all and I'm sorry for all this thread has not to be exactly a podman's bug! ;^) |
Beta Was this translation helpful? Give feedback.
-
Well uid mapping is part of how rootless podman works. You likely want to add something like And if this is really a permission errors than the QT error is just bad as it doesn't mention that (or even which file it tried to open) |
Beta Was this translation helpful? Give feedback.
-
Hi again! Well, the first command has a typo: " Here are the file/folder permissions: root@869ed4e1ba7b:/# ls -lAF /
total 140
drwxr-xr-x 2 root root 4096 Apr 5 13:34 app/
drwxr-xr-x 1 root root 4096 Apr 6 06:57 bin/
-rw-r--r-- 1 root root 76 Apr 6 06:57 build_version
drwxr-xr-x 2 root root 12288 Apr 5 13:34 command/
drwxrwxrwx 1 1000 users 4096 Apr 6 07:23 config/
drwxr-xr-x 1 root root 4096 Apr 6 06:55 defaults/
drwxr-xr-x 5 root root 340 Apr 15 10:03 dev/
-rwxr-xr-x 1 root root 31108 Jan 1 1970 docker-mods*
drwxrwxrwx 1 1000 users 4096 Apr 14 21:03 downloads/
drwxr-xr-x 1 root root 4096 Apr 15 10:03 etc/
drwxr-xr-x 2 root root 4096 Apr 5 13:34 home/
-rwxr-xr-x 1 root root 1012 Oct 10 2024 init*
drwxr-xr-x 1 root root 4096 Apr 5 13:34 lib/
drwxr-xr-x 2 root root 4096 Apr 5 13:34 lsiopy/
drwxr-xr-x 5 root root 4096 Apr 5 13:34 media/
drwxr-xr-x 2 root root 4096 Apr 5 13:34 mnt/
drwxr-xr-x 2 root root 4096 Apr 5 13:34 opt/
drwxr-xr-x 6 root root 4096 Apr 5 13:34 package/
dr-xr-xr-x 224 root root 0 Apr 15 10:03 proc/
drwxr-xr-x 2 root root 12288 Apr 6 06:57 qbt/
drwx------ 2 root root 4096 Apr 5 13:34 root/
drwxr-xr-x 1 root root 4096 Apr 15 10:03 run/
drwxr-xr-x 1 root root 4096 Apr 5 13:34 sbin/
drwxr-xr-x 2 root root 4096 Apr 5 13:34 srv/
dr-xr-xr-x 11 root root 0 Apr 15 10:03 sys/
drwxrwxrwt 2 root root 4096 Apr 5 13:34 tmp/
drwxr-xr-x 1 root root 4096 Apr 6 06:55 usr/
drwxr-xr-x 1 root root 4096 Apr 5 13:34 var/
root@869ed4e1ba7b:/#
root@869ed4e1ba7b:/# ls -lAF /config
total 0
drwxrwxrwx 1 1000 users 4096 Apr 6 07:23 .cache/
drwxr-xr-x 1 101000 101000 4096 Apr 15 10:03 qBittorrent/
root@869ed4e1ba7b:/# though I think it still needs a "refining"; that: " |
Beta Was this translation helpful? Give feedback.
-
I am pretty sure that is the correct syntax though maybe it doesn't work right via remote. |
Beta Was this translation helpful? Give feedback.
-
Just as a recap, for your info... I'm launching Podman from Windows 11, with this (the "latest") command:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Issue Description
Hi, all!
Recently, i had to move from Docker to Podman. And then, I tried to launch QBitTorrent, but...
This is my command;
The container starts but does not work. Logs:
[terminal]
[docker container]
I know you don't support Podman, but this seems to be a problem related with: "QT" and a file locked somewhere.
Can You please give it a try?
Thanks in advance. ;^)
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
The same message one and over again:
"QtLockedFile::lock(): file is not opened"
Describe the results you expected
http://localhost:8080 working.
But the browser says no data is received.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
No
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
Beta Was this translation helpful? Give feedback.
All reactions