From ff28543d6f63fef7ceeaab24b2b76ac95ffe189b Mon Sep 17 00:00:00 2001 From: thespad Date: Wed, 26 Jun 2024 21:33:29 +0100 Subject: [PATCH] Clarify UID as GID can vary --- docs/misc/read-only.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/misc/read-only.md b/docs/misc/read-only.md index d23d6ed66..868a3d130 100644 --- a/docs/misc/read-only.md +++ b/docs/misc/read-only.md @@ -30,7 +30,7 @@ Will mount its filesystem as read-only, and that cannot then be changed without Our images use s6 as a supervisor and that needs to be able to write its service files to `/run`; many applications expect to be able to write to their working directory, changing UIDs and GIDs requires writing to `/etc/passwd` & `/etc/group`, installing new packages requires writing to numerous locations, and as discussed above, mods need to be extracted to the container filesystem. In short, there are some heavy limitations around read-only operation of our images: -* The PUID & PGID variables will not have any effect, the container will run applications as 911:911, and will apply those permissions to `/config`. +* The PUID & PGID variables will not have any effect, the container will run applications with a UID of 911, and will apply those permissions to `/config`. * The UMASK variable will not have any effect * Docker Mods will not be run * Custom Services will not be run