Publish flavor with libtorrent 2.0

[MoshiBin]

Seeing as the default for qBittorrent releases is using libtorrent 2.0, it might be a good idea to also publish official images with libtorrent 2.0 - perhaps even making those the default.

I'm offering to submit a PR that will either:

1. Change the default to libtorrent 2.0 when building the image
2. Build twice: Once with lt1.2 and once with lt1.2. Then publish two images with a suffix to their tag that clearly shows if this is lt1.2 or lt2.0.

Please let me know if you're interested in this contribution.

[Chocobo1]

Seeing as the default for qBittorrent releases is using libtorrent 2.0, ...

It is not. See https://sourceforge.net/projects/qbittorrent/files/qbittorrent-win32/qbittorrent-5.1.1/ The default installer is qbittorrent_5.1.1_x64_setup.exe. The lt20 version is sort of an addition to the default one.

Please let me know if you're interested in this contribution.

I would like to handle it myself.

it might be a good idea to also publish official images with libtorrent 2.0 - perhaps even making those the default.

Since we are here, have you actually ran qbt with lt20? How does it work for you? Based on user reports, lt20 may have noticeable (or even significant) performance issues. And that is the main reason why I haven't provided lt20 yet.

[MoshiBin]

My bad about the default - I misread the qbt CMakeList.

I've been trying to debug some performance issues with my qbt instance. I was previously using the LinuxServer image, which does default to lt20. It started hogging memory until it crashed. I tried both changing disk IO mode and moving to lt12 but neither of these things helped.

Then I found out that there was an official Docker image, so I moved to it instead of the linuxserver image. Unfortunately, this also didn't help and my instance (using clean config but with pre-existing fastresume files) still hogs private memory. It did help that this image has easy access to a shell, so I was able to see that it wasn't just mmaping files - it's actual private memory that's increasing.

Seeing as this instance was running for months without issues, I believe it's not related directly to lt20. It might be an issue with a specific fastresume file, or it might be related to the number of torrents the client holds (~3k).

None of this is relevant to the image, of course. Still, I'd really appreciate the ability to use lt20 - and the ability to explicitly say which lt version I want to use, in case the default changes eventually.

[iamtherobin]

I too would be interested in testing out a lt2.0 nox container. If you provided two containers, it would be simple enough to switch between them on a docker system if there is a problem with lt2.0 or just deploy two container side by side for testing purposes.

[Chocobo1]

I too would be interested in testing out a lt2.0 nox container.

Set QBT_VERSION to alpha: https://github.com/qbittorrent/docker-qbittorrent-nox?tab=readme-ov-file#environment-variables

[rotem-bar]

@Chocobo1 Hey, thanks for your work on this, is there any chance you can publish the source of the alpha tags? I see that its being pushed but its not source-available.

Would also be nice if we can get it pushed and released through github actions (even if it stays alpha tagged) because of the extra architectures (personally I need an arm64 build)

[alvitali]

Would love to see a tag with lt2.0 published so I can finally make the switch from the linuxserver image