Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qBittorrent folder structure has changed in v4.3.0+ #85

Closed
ghost opened this issue Nov 12, 2020 · 1 comment · Fixed by #86
Closed

qBittorrent folder structure has changed in v4.3.0+ #85

ghost opened this issue Nov 12, 2020 · 1 comment · Fixed by #86

Comments

@ghost
Copy link

ghost commented Nov 12, 2020

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

  1. Install qBittorrent using the linuxserver.io container image for v4.3.0 or later.
  2. 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

@project-bot project-bot bot added this to To do in Issue & PR Tracker Nov 12, 2020
@github-actions
Copy link

Thanks for opening your first issue here! Be sure to follow the issue template!

Issue & PR Tracker automation moved this from To do to Done Nov 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging a pull request may close this issue.

0 participants