Open TrueOsiris opened 4 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
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.
I can't replicate this with a clean container; the plugins list is populated with the default plugins, and I can enable them all without error.
Please make sure the plugins you're using are actually maintained, because at a glance a lot of the 3rd party plugins are still python 2.x, which will never work, and many expect old versions of python 3; the container ships with 3.12.3 at this point.
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.
Is there an existing issue for this?
Current Behavior
When trying to add any egg / plugin or trying to enable the ones that ought to be built-in, I get this in my container log
Also, the default plugin list is empty, while this version should already contain a list of plugins that can be enabled.
I'm starting this with an unaltered config, running on unraid linux, using docker compose. folder rights seem to be fine on the config folder.
Expected Behavior
I should be able to install eggs / plugins without python errors in the docker log.
Steps To Reproduce
see other descriptions. I'm running the container through docker compose and I'm trying to add a plugin via the webUI.
Environment
CPU architecture
x86-64
Docker creation
Container logs