mirror/archivebox
1
0
Fork 0
mirror of https://github.com/pirate/ArchiveBox.git synced 2025-08-22 06:03:23 +02:00
Code Issues Releases Wiki Activity

Updated Configuration (markdown)

Nick Sweeting
2024-02-29 01:54:11 -08:00
parent 8938bb7241
commit aa7130d340
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
Configuration.md

@@ -61,12 +61,15 @@ User and Group ownership to set the output directory and file contents to. **On
This is useful on some Docker setups when you want the data dir to be owned by the same UID/GID on the host and inside the container.
`PUID=0` is not allowed ([do not run as root](https://github.com/ArchiveBox/ArchiveBox/wiki/Security-Overview#do-not-run-as-root)), and `PGID=0` is allowed but not recommended.
`PUID=0` is not allowed ([do not run as root](https://github.com/ArchiveBox/ArchiveBox/wiki/Security-Overview#do-not-run-as-root)), and `PGID=0` is allowed but not recommended. `PUID`s and `PGID`s below `100` cause many issues because they're often [already in use](https://github.com/ArchiveBox/ArchiveBox/discussions/1366) by an existing linux user in docker, if the files must be owned by a low value ID e.g. `33` (`www-data`), you may need to use [`bindfs`](https://github.com/clecherbauer/docker-volume-bindfs) to remap the permissions.
Make sure if using NFS/SMB/FUSE that the volume allows setting ownership on files (e.g. don't set `root_squash` or `all_squash` on NFS shares).
*Learn more:*
- https://docs.linuxserver.io/general/understanding-puid-and-pgid/
- https://github.com/ArchiveBox/ArchiveBox/wiki/Troubleshooting#docker-permissions-issues
- https://github.com/ArchiveBox/ArchiveBox/issues/1304
- https://github.com/ArchiveBox/ArchiveBox/discussions/1366
- https://github.com/ArchiveBox/ArchiveBox/blob/main/bin/docker_entrypoint.sh
*Related options:*