FEATURE REQUEST: allowing setting PUID/GUID #31

New Issue

saavagebueno · 2025-11-20T04:19:15-05:00

saavagebueno commented

2025-11-20 04:19:15 -05:00

Originally created by @bcurran3 on GitHub (May 21, 2020).

Of course I did NOT follow the instructions for setting up the config.json...

After initial install and run I instantly received:

If we could set PUID/GUID in the environment variables, setup would be simpler. (HINT: Look at all the linuxserver containers.)

Not sure of the setup, but running as root would also solve the problem!

Originally created by @bcurran3 on GitHub (May 21, 2020). Of course I did NOT follow the instructions for setting up the config.json... After initial install and run I instantly received: ![image](https://user-images.githubusercontent.com/14026600/82609259-06728680-9b71-11ea-9800-dcacaf9ab6ba.png) If we could set PUID/GUID in the environment variables, setup would be simpler. (HINT: Look at all the linuxserver containers.) Not sure of the setup, but running as root would also solve the problem!

saavagebueno closed this issue

2025-11-20 04:19:15 -05:00

saavagebueno commented

2025-11-20 04:19:15 -05:00

@qdm12 commented on GitHub (May 21, 2020):

Linuxserver containers do run as root and then drop it, which is less secured (although better than just root). What you can do however is run the container with a certain user id and group id which achieves the same thing but runs entirely with that user+group, I have a note in the readme for that 😉

You could change the user ID, for example with 1001, by running the container with --user=1001

On docker-compose, see this

@qdm12 commented on GitHub (May 21, 2020): Linuxserver containers do run as root and then drop it, which is less secured (although better than just root). What you can do however is run the container with a certain user id and group id which achieves the same thing but runs entirely with that user+group, I have a note in the readme for that :wink: > You could change the user ID, for example with 1001, by running the container with --user=1001 On docker-compose, see [this](https://docs.docker.com/compose/compose-file/#domainname-hostname-ipc-mac_address-privileged-read_only-shm_size-stdin_open-tty-user-working_dir)

saavagebueno commented

2025-11-20 04:19:15 -05:00

@bcurran3 commented on GitHub (May 21, 2020):

I miscommunicated.

Honestly I don't care if the program runs as DonaldJTrump in the children group. This is really a continuation of a theme... to get rid of:

 touch data/config.json
 # Owned by user ID of Docker container (1000)
 chown -R 1000 data
 # all access (for creating json database file data/updates.json)
 chmod 700 data
 # read access only
 chmod 400 data/config.json

I'm hoping #61 and/or #62 will accomplish the same goal.

@bcurran3 commented on GitHub (May 21, 2020): I miscommunicated. Honestly I don't care if the program runs as DonaldJTrump in the children group. This is really a continuation of a theme... to get rid of: ``` touch data/config.json # Owned by user ID of Docker container (1000) chown -R 1000 data # all access (for creating json database file data/updates.json) chmod 700 data # read access only chmod 400 data/config.json ``` I'm hoping #61 and/or #62 will accomplish the same goal. ![image](https://user-images.githubusercontent.com/14026600/82628532-ee672b00-9ba1-11ea-9164-6574aee7b18b.png)

saavagebueno referenced this issue

2025-11-20 04:25:21 -05:00

[PR #35] [MERGED] Record new IP for Infomaniak #585

saavagebueno referenced this issue

2025-11-20 04:25:21 -05:00

[PR #36] [MERGED] Added IP methods and cycle IP method + unit tests #587

saavagebueno referenced this issue

2025-11-20 04:25:21 -05:00

[PR #34] [MERGED] Fix #31, add support for Infomaniak #589

Sign in to join this conversation.