-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
[BUG] Jackett WebGUI Portainer Issue #152
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
The container works fine according to our smoke tests: https://ci-tests.linuxserver.io/linuxserver/jackett/latest/index.html Seems like to potentially might be permissions issues but you'd have to test with true compose. We do not support nor recommend portainer for deployment of our containers. |
Thanks! I'll double check and will report back if I find anything. |
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 is locked due to inactivity |
Is there an existing issue for this?
Current Behavior
When I use the "LinuxServer.io" Jackett docker compose example inside Portainer and use the PUID and PGID of 1000, the WebUI is not accessible and the container will not load. The only way I can get the container to load and the WebUI to work is if I set the PUID and PGID to 0 (root). When I set it back to 1000 and inspect the logs, the container won't even finish loading or pulling the image. If I switch it back to 0, it loads everything perfectly fine.
I have also created a user called "docker" that is used throughout the network for various containers with sudo privileges. I matched the PUID and PGID for that user and tried that and still does not work.
Expected Behavior
Jackett stack should fully load if using PGID/PUID of 1000.
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: