You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In qBittorrent v4.2.5 and earlier, the application's data was saved in /config/data/qBittorrent and /config/qBittorrent. This changed with the release of v4.3.0. All application data is now saved in /config/qBittorrent and the old folder structure, while it still works, has been deprecated, with a warning being printed if it is detected at startup.
I think it's the job of qBittorrent itself to migrate the application data from the legacy directory to the new directory if or when support for the legacy folder structure is removed in a future version, but this issue isn't about that. This issue is about the linuxserver.io image unconditionally creating the /config/data directory at startup even when one is using qBittorrent v4.3.0 or later, where this folder remains unused and empty.
I'll be opening a pull request to fix this issue shortly.
Steps to Reproduce
Install qBittorrent using the linuxserver.io container image for v4.3.0 or later.
Observe the /config/data directory being created on container startup even though these qBittorrent versions don't use it.
Environment
OS: Debian 10 CPU architecture: x86_64 How docker service was installed: From the official Docker repository
The text was updated successfully, but these errors were encountered:
Explanation
In qBittorrent v4.2.5 and earlier, the application's data was saved in
/config/data/qBittorrent
and/config/qBittorrent
. This changed with the release of v4.3.0. All application data is now saved in/config/qBittorrent
and the old folder structure, while it still works, has been deprecated, with a warning being printed if it is detected at startup.I think it's the job of qBittorrent itself to migrate the application data from the legacy directory to the new directory if or when support for the legacy folder structure is removed in a future version, but this issue isn't about that. This issue is about the linuxserver.io image unconditionally creating the
/config/data
directory at startup even when one is using qBittorrent v4.3.0 or later, where this folder remains unused and empty.I'll be opening a pull request to fix this issue shortly.
Steps to Reproduce
/config/data
directory being created on container startup even though these qBittorrent versions don't use it.Environment
OS: Debian 10
CPU architecture: x86_64
How docker service was installed: From the official Docker repository
The text was updated successfully, but these errors were encountered: