Open JohnnyTendo opened 23 hours ago
Hey! So to be clear, your host system's user with the user and group ID of 1000 have complete write access to /srv/satisfactory-server/config
?
Yes the user I'm using for docker containers does have write permissions to /srv/satisfactory-server/config
. @____ is my host system
[docker@____ config]$ id
uid=1000(docker) gid=1000(docker) Gruppen=1000(docker),10(wheel)
[docker@____ config]$ pwd
/srv/satisfactory-server/config
[docker@____ config]$ ls -alu
drwxrwxrwx 2 docker docker 4096 9. Okt 08:08 .
drwxr-xr-x 8 root root 4096 8. Okt 15:15 ..
[docker@____ config]$ touch fooBarz
[docker@____ config]$ ls -alu
drwxrwxrwx 2 docker docker 4096 9. Okt 08:09 .
drwxr-xr-x 8 root root 4096 8. Okt 15:15 ..
-rw-rw-r-- 1 docker docker 0 9. Okt 08:09 fooBarz
Experiencing issues? Check our Troubleshooting FAQ wiki!
Describe the Bug
I'm trying to start the satisfactory-server container by using the provided docker-compose.yml. After running the docker-compose up command, the container gets stuck in a restart loop. After running the container without the detached flag (docker-compose up) I got the log output below. The init.sh script exits after checking for write permissions on the /config dir, which is missing. The container itself reports that it is in a healthy state (I'm using portainer to monitor and orchestrate my containers). I tried several different attempts with slight modifications of the mounted volume (tested every change by itself but also every possible combination):
Your Runtime Command or Docker Compose File
Debug Output
System Specs (please complete the following information):
Logs
Additional Context
I already tried using a clone of the repo and it's dockerfile, to overwrite the init.sh and also to bypass it completely, to manually start it while being attached to the container. While being attached to the container, I can freely write to the /config dir with the steam user specified in the init.sh.
EDIT: I initaly wrote 'chown 777 config' in the description, which of course, doesn't make any sense. I meant 'chmod 777 config'