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 the current build the dependencies for socks5 are missing and therefore the proxy plugin (https://flexget.com/en/Plugins/proxy) does not work with socks5.
Expected Behavior
The required dependencies should be added so socks5 support is available for the proxy plugin.
pip install pysocks requests[socks] urllib3[socks] should do the job.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
You might consider using the official Docker image maintained by the FlexGet team. If you encounter any issues, you can report them directly to the FlexGet repository: FlexGet Issues.
Using the official image ensures you receive bug fixes more quickly.
You might consider using the official Docker image maintained by the FlexGet team. If you encounter any issues, you can report them directly to the FlexGet repository: FlexGet Issues.
Using the official image ensures you receive bug fixes more quickly.
Sadly same issue with official image -> ftp_list is not working - stating missing dependency 'ftputil' - even though ftputil is installed
You might consider using the official Docker image maintained by the FlexGet team. If you encounter any issues, you can report them directly to the FlexGet repository: FlexGet Issues.
Using the official image ensures you receive bug fixes more quickly.
Sadly same issue with official image -> ftp_list is not working - stating missing dependency 'ftputil' - even though ftputil is installed
I’ve submitted a PR that might resolve your issue if it gets merged.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
At first glance, it seems to be incompatibilites between pip and uv.
Unfortunately many upstream projects are switching to uv because it installs packages a lot faster. However, it is not really a drop in replacement for pip as it lacks many features that pip has. Our universal package installer mod uses pip to install packages runtime.
I personally had to deal with uv first in our Home Assistant image and had to resort to some ugly hacks to make runtime install of packages work (HACS plugins).
When I get a chance, I'll look at this image to figure out a solution. Perhaps the universal package installer needs some compatibility baked in for uv.
PR #28 will fix the universal-package-install mod compatibility so it can install pip packages.
Any plugin deps you need can be installed via that mod.
@Stiefmeister in your post I noticed that you were using incorrect package names. The INSTALL_PIP_PACKAGES var needs to contain python package names (you can check on pypi). There is a separate var for os repo package names. For instance, py3-pysocks is not a python package name, it should be pysocks.
Activity
github-actions commentedon Feb 6, 2025
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Noki commentedon Feb 6, 2025
Note: I used a custom entrypoint to add the missing dependencies previously, but it would be really good to just have them by default.
LinuxServer-CI commentedon Mar 8, 2025
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Noki commentedon Mar 9, 2025
This issue still persists...
Stiefmeister commentedon Mar 14, 2025
Can confirm that this issue is still present, even when using ENV variables:
So all plugins requiring additional python packages are affected and do not work anymore:
https://flexget.com/en/Plugins/proxy
https://flexget.com/Plugins/ftp_list
https://flexget.com/Plugins/decompress
Flexget will complain that packages/dependencies are missing.
vivodi commentedon Mar 17, 2025
You might consider using the official Docker image maintained by the FlexGet team. If you encounter any issues, you can report them directly to the FlexGet repository: FlexGet Issues.
Using the official image ensures you receive bug fixes more quickly.
Stiefmeister commentedon Mar 25, 2025
Sadly same issue with official image -> ftp_list is not working - stating missing dependency 'ftputil' - even though ftputil is installed
vivodi commentedon Mar 25, 2025
I’ve submitted a PR that might resolve your issue if it gets merged.
Stiefmeister commentedon Mar 26, 2025
When switching back to versions 3.11 / 3.12 dependencies are not an issue, so it is relatedonly to newer Python / Flexget versions
LinuxServer-CI commentedon Apr 25, 2025
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
9 remaining items
LinuxServer-CI commentedon Sep 16, 2025
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
vivodi commentedon Sep 16, 2025
This issue persists.
LinuxServer-CI commentedon Oct 17, 2025
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
vivodi commentedon Oct 17, 2025
Blocked by astral-sh/uv#13129
aptalca commentedon Oct 17, 2025
I just saw this issue.
At first glance, it seems to be incompatibilites between pip and uv.
Unfortunately many upstream projects are switching to uv because it installs packages a lot faster. However, it is not really a drop in replacement for pip as it lacks many features that pip has. Our universal package installer mod uses pip to install packages runtime.
I personally had to deal with uv first in our Home Assistant image and had to resort to some ugly hacks to make runtime install of packages work (HACS plugins).
When I get a chance, I'll look at this image to figure out a solution. Perhaps the universal package installer needs some compatibility baked in for uv.
aptalca commentedon Oct 17, 2025
Well, I wish someone posted a container log. We could have identified and fixed this very quickly.
The container is just missing
pipasuv venv /lsiopycreates the venv without pip. It's an easy fix.aptalca commentedon Oct 17, 2025
PR #28 will fix the universal-package-install mod compatibility so it can install pip packages.
Any plugin deps you need can be installed via that mod.
@Stiefmeister in your post I noticed that you were using incorrect package names. The
INSTALL_PIP_PACKAGESvar needs to contain python package names (you can check on pypi). There is a separate var for os repo package names. For instance,py3-pysocksis not a python package name, it should bepysocks.LinuxServer-CI commentedon Nov 17, 2025
This issue is locked due to inactivity