[Feature] Allow configuration of User ID and Group ID used to run service in Docker #1332

Closed
opened 2026-02-28 19:40:40 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @RyanMelena on GitHub (Aug 13, 2024).

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

Would like to be able to configure the user and group Actual runs under within Docker for improved security and volume mount file permissions.

Describe your ideal solution to this problem

Support PUID and PGID arguments from Docker as standardized by linuxserver.io: https://docs.linuxserver.io/general/understanding-puid-and-pgid/

Teaching and learning

Update Configuring the Server documentation ( https://actualbudget.org/docs/config/ ) with new PUID and PGID environment variables.

Originally created by @RyanMelena on GitHub (Aug 13, 2024). ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [X] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? Would like to be able to configure the user and group Actual runs under within Docker for improved security and volume mount file permissions. ### Describe your ideal solution to this problem Support PUID and PGID arguments from Docker as standardized by linuxserver.io: https://docs.linuxserver.io/general/understanding-puid-and-pgid/ ### Teaching and learning Update `Configuring the Server` documentation ( https://actualbudget.org/docs/config/ ) with new PUID and PGID environment variables.
GiteaMirror added the featureneeds votes labels 2026-02-28 19:40:40 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Aug 13, 2024):

Thanks for sharing your idea!

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

@github-actions[bot] commented on GitHub (Aug 13, 2024): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
Author
Owner

@RyanMelena commented on GitHub (Aug 28, 2024):

Example implementation here: https://github.com/RyanMelena/actual-server-custom

@RyanMelena commented on GitHub (Aug 28, 2024): Example implementation here: https://github.com/RyanMelena/actual-server-custom
Author
Owner

@m3Lith commented on GitHub (Sep 25, 2024):

You can kind of achieve that by passing --user PUID:PGID, or by using the user directive inside compose file. Just would need to create the root config dir manually first (or chown and restart container).

@m3Lith commented on GitHub (Sep 25, 2024): You can kind of achieve that by passing `--user PUID:PGID`, or by using the `user` directive inside compose file. Just would need to create the root config dir manually first (or `chown` and restart container).
Author
Owner

@dasunsrule32 commented on GitHub (Mar 11, 2025):

This should definitely happen. If you create new files, even with PUID and PGID defined, the new files will be owned by root and the new files have to be chown'd. Not ideal.

@dasunsrule32 commented on GitHub (Mar 11, 2025): This should definitely happen. If you create new files, even with `PUID` and `PGID` defined, the new files will be owned by `root` and the new files have to be `chown`'d. Not ideal.
Author
Owner

@dasunsrule32 commented on GitHub (Mar 11, 2025):

And you can just configure your compose.yaml to run as the user needed: user: 1000:1000.

@dasunsrule32 commented on GitHub (Mar 11, 2025): And you can just configure your `compose.yaml` to run as the user needed: ` user: 1000:1000`.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#1332