PUID and PGID not accepted on Synology NAS

[marchoeppner]

Hi,

I was previously able to run this docker container with Foundry v12 on my Synology NAS (see: https://foundryvtt.wiki/en/setup/hosting/synology-with-docker).

ONe of the things needed was to use PUID and PGID to make sure the container uses the user that has ownership of the local data directory.

After months of not having messed with it, I wanted to install V13; wiped the old stuff and went ahead to configure the container and environment. But the container insists on starting as 1000:1000. And that does not exist on a Synology System. I could force-create such a user, probably, but this is clearly not intended by the OS (i.e. you cannot create users or groups with specific ids via the GUI).

Long story short - did anything change that would explain why PUID and PGID are no longer used?

Cheers,
Marc

[marchoeppner]

Just to confirm, I fetched the last version of the V12 container, and that lets me boot up Foundry just fine.

[marchoeppner]

Found this eventually:
#1197

Will update this post if I found a way to make that work on the Synology.

[marchoeppner]

Oddly, after two tries, creating the local data directory from the command line and chown'ing it to 1000:1000 then utlimately worked.

[marchoeppner]

One annoyance:

chown'ing the data folder to 1000:1000, which does not exist on a Synology system, hides the folder in the GUI. So when updating the SSL cert, I have to first chown the folder to my admin user, upload the new cert, and re-chowning it to 1000:1000.

I am sure there was a reason for making the default user 1000:1000 and preventing users to change it to something more appropriate on the host (as was previously possible with PUID, PGID), but this is honestly a little annoying.