fix: disk image
Build and Publish Container / Publish Linux container (push) Successful in 4m11s

This commit is contained in:
2026-10-05 18:09:15 -04:00
parent 79e953bbe7
commit c79aad1cb9
4 changed files with 145 additions and 1 deletions
+6
View File
@@ -22,6 +22,12 @@ result, and completion percentage in Dockhand or with `docker compose logs -f`.
Failed batches also include SteamCMD's output tail so network, subscription, and
filesystem errors are visible directly in the container log.
SteamCMD is forced to use `/opt/steamcmd` so Workshop content always lands in
the mounted volume. On the first `I/O Operation Failed` result, transient `.acf`,
download, and temp state is moved into `.progression-recovery`; completed mod
directories are left untouched. Startup also checks that the volume has enough
free space for the remaining Steam metadata estimate.
The image does not switch Unix users at startup because some rootless and
capability-restricted container hosts block `setuid`. The process remains inside
the container's user namespace and writes directly to its named volumes.