vh/NetAlertX
1
0
Fork 0
mirror of https://github.com/jokob-sk/NetAlertX.git synced 2026-04-04 01:01:35 -07:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity

DOCS: cleanup

Browse Source 
Signed-off-by: jokob-sk <jokob.sk@gmail.com>
This commit is contained in:
jokob-sk
2026-01-14 13:18:33 +11:00
parent ccbac347aa
commit 08db1c658e
2 changed files with 40 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/FILE_PERMISSIONS.md
View File

@@ -38,9 +38,9 @@ NetAlertX requires certain paths to be writable at runtime. These paths should b
> All these paths will have **UID 20211 / GID 20211** inside the container. Files on the host will appear owned by `20211:20211`.
## Eunning as `root`
## Running as `root`
You can change the default PUID and GUID with env variables:
You can override the default PUID and PGID using environment variables:
```yaml
...
@@ -50,6 +50,16 @@ You can change the default PUID and GUID with env variables:
...
```
To run as the root user, it usually looks like this (verify the IDs on your server first by executing `id root`):
```yaml
...
environment:
PUID: 0 # Runtime PUID override, set to 0 to run as root
PGID: 100 # Runtime PGID override
...
```
### Solution
1. **Run the container once as root** (`--user "0"`) to allow it to correct permissions automatically: