New System PUID:GUID problem

[foolishrunner]

Hey, I've been using the image flawlessly for a while now and recently migrated my server to new hardware and ubuntu 22.04, from 20.04.

After a system reboot the valheim servers constantly restart if I have the PUID: in the docker compose file set to 1000, my user. I own all the files/dirs etc. If I remove the PUID / GUID from the docker file it sets speech-dispatcher:x:111:29:Speech Dispatcher to all dirs/files, but it runs fine.

valheimServer01 | 0 1 * * * BASH_ENV=/env.sh /bin/bash /home/steam/scripts/auto_update.sh >> /home/steam/valheim/logs/auto-update.out 2>&1
valheimServer01 | chmod: changing permissions of '/home/steam/cron.d/auto-update': Operation not permitted
valheimServer01 exited with code 0

valheim_server.err
[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
CAppInfoCacheReadFromDiskThread took 4 milliseconds to initialize
Setting breakpad minidump AppID = 892970
SteamInternal_SetMinidumpSteamID: Caching Steam ID: ### [API loaded no]
[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded.

If I run - docker compose up -d --force-recreate I can get the server to start up.

environment:
  PUID: 1000
  PGID: 1000

Old system inside docker container /etc/passwd- steam:x:1000:65534::/home/steam:/bin/bash
New system inside docker container /etc/passwd - steam:x:111:1000::/home/steam:/bin/bash

Any ideas?

[foolishrunner]

Have pulled version 2.1.2 which is what I had last pulled on the previous hardware and it's working.

[foolishrunner]

v3.0.0
💥 Breaking Change

rework shell and docker logic with reworked readme https://github.com/mbround18/valheim-docker/pull/846 ([@mbround18](https://github.com/mbround18))

Note: this reworks the user permissions which had a major change in later versions of ubuntu. Expected PUID is 111 and GUID can be dynamic.

[foolishrunner]

Can anyone explain to me why or how to work around my local user for PUID 111 is speech-dispatcher?

[mbround18]

Set a group id to your local user id and use the same group id for the docker container

[mbround18]

1. Create a new group named valheim:

sudo groupadd valheim

2. Add your current user to the valheim group:

sudo usermod -a -G valheim $USER

3. Verify that the group was created and your user was added successfully:

groups $USER

4. Find the group ID (GID) of the valheim group:

getent group valheim

This command will output something like valheim:x:1001:, where 1001 is the GID.

5. Set the permissions for the directories to be group writable, readable, and executable:

sudo chown -R :valheim ./saves ./server ./backups
sudo chmod -R 775 ./saves ./server ./backups

6. Update your docker-compose.yml file to set the PGID:

Open your docker-compose.yml file in a text editor and modify it as follows:

version: '3'
services:
  valheim:
    image: mbround18/valheim:latest
    container_name: valheim
    environment:
      - PGID=1001  # Replace with the actual GID from step 4
    volumes:
      - ./saves:/home/steam/.config/unity3d/IronGate/Valheim
      - ./server:/home/steam/valheim
      - ./backups:/home/steam/backups
    ports:
      - "2456-2458:2456-2458/udp"
    restart: unless-stopped

Replace 1001 with the actual GID you found in step 4. You can also dynamically set the PUID using the id -u command to get your current user ID.

7. Restart your Docker Compose services to apply the changes:

docker-compose down
docker-compose up -d

This will recreate the container with the new PGID settings.

[YodaDaCoda]

I'm having this same issue - I have PUID=1000 and PGID=1000 specified in my compose.yml. I can see in the /etc/passwd that the steam user that's created retains the uid of 111 but inherits the gid of 1000. The user/group of /home/steam/cron.d/auto-backup is 1000/1000 (which shows up as 1000/steam).

If the docker container stops, e.g. due to restarting the host, then I encounter this error when re-starting the container. If I instead delete the container and re-create it, I do not encounter this issue.

Workaround: re-create the container instead of re-starting it.

Bug: permissions need some amendment - PUID doesn't seem to be respected in all cases.

From what I can see of the Dockerfile.valheim and entrypoint.sh, this can probably be resolved with a usermod -u $PUID steam to change the steam user's uid, and slight change to entrypoint.sh:159 to make it affect the home directory rather than only the dotfiles within sudo chown -R "$PUID:$PGID" "$HOME" /home/steam/ (remove the .* from the end).

[dkurzaj]

I'm having the same issue indeed.

[mbround18]

im working on this issue, since this is a rootless container as of version 3, the user id isnt taken into account. This change was due to how the later version of ubuntu handles user ids which now the containers initial user starts at 111 vs 1000. I can take a look around the shell and see if i can get this functioning as intended.