mirror
/
Jackett
mirror of https://github.com/Jackett/Jackett
1
0
Fork 0
Code Issues Releases Wiki Activity

Updated Troubleshooting (markdown)

garfield69 2024-04-22 13:19:01 +12:00
parent 11d2976fb2
commit bd0159b472
1 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
Troubleshooting.md

@ -278,9 +278,19 @@ See [[How to provide a Jackett Enhanced log for a ticket|https://github.com/Jack
[[Return to Index|https://github.com/Jackett/Jackett/wiki/TroubleShooting/#index]]
***
## Jackett is running with root privileges. You should run Jackett as an unprivileged user.
Explanation TBP
If you are doing this on purpose for some yet to be determined good reason then you can set an Environment Variable `DisableRootWarning` and the message will be suppressed. TBC
It seems that your Jackett has been set up with root privileges.
Jackett should not be run as root under any circumstance. Even if it's running inside a container, a jail or a virtual environment the user can make a mistake mounting the filesystem volume and Jackett will have root access to the files.
However, if you choose to ignore this warning and want to proceed without being reminded about this security risk, then you can set an Environment Variable `DisableRootWarning` and the message will be suppressed.
- Docker: Environment variables can be set in the docker-compose.yml file or in the Docker CLI command.
- add to your cli command `-e DisableRootWarning=true`
- Add to your compose.yml
```yaml
environment:
- LOG_LEVEL=${LOG_LEVEL:-info}
```
- Linux: Run `export DisableRootWarning=true` and then run jackett in the same shell.
- Windows: Open cmd.exe, run `set DisableRootWarning=true` and then run Jackett.exe in the same shell.
[[Return to Index|https://github.com/Jackett/Jackett/wiki/TroubleShooting/#index]]
***