From a25fd0db84e628498f2f3bbe649657a4faf0f4e6 Mon Sep 17 00:00:00 2001
From: JJGadgets <git@jjgadgets.tech>
Date: Sat, 27 May 2023 03:28:53 +0800
Subject: [PATCH] fix(satisfactory): UID 0 for now

the entrypoint (CMD) script init.sh does an `id -u` of current UID before dropping privs, and will exit as error if not UID 0. will open issue to ask if running as true rootless due to K8s is possible via new envvar ROOTLESS=k8s or something like that
---
 kube/3-deploy/2-apps/satisfactory/app/hr.yaml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/kube/3-deploy/2-apps/satisfactory/app/hr.yaml b/kube/3-deploy/2-apps/satisfactory/app/hr.yaml
index 6ef78016..cbd946f1 100644
--- a/kube/3-deploy/2-apps/satisfactory/app/hr.yaml
+++ b/kube/3-deploy/2-apps/satisfactory/app/hr.yaml
@@ -20,8 +20,8 @@ spec:
       repository: docker.io/wolveix/satisfactory-server
       tag: v1.4.8@sha256:56ca73cb8a64e7bedfe0b72c9490ce1d32e547a16c753ffcb7e96c8364e8c348
     podSecurityContext:
-      runAsUser: &uid ${APP_UID_SATISFACTORY}
-      runAsGroup: *uid
+      runAsUser: 0 # image uses PUID & PGID to fix permissions for Docker users, which requires starting as rootless :sadge: TODO: open issue to allow envvar to configure if rootless is allowed
+      runAsGroup: &uid ${APP_UID_SATISFACTORY}
       fsGroup: *uid
       fsGroupChangePolicy: Always
     env: