Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow specifying PUID and PGID when running the Docker image #3434

Open
mikegleasonjr opened this issue Jul 6, 2022 · 4 comments
Open

Allow specifying PUID and PGID when running the Docker image #3434

mikegleasonjr opened this issue Jul 6, 2022 · 4 comments
Labels
enhancement New feature or request pinned

Comments

@mikegleasonjr
Copy link

mikegleasonjr commented Jul 6, 2022

Describe what you are trying to accomplish and why in non technical terms
Like all linuxserver.io images, I would like to be able to specify the PGID and the PUID of the Frigate process in the Docker container so the files created by Frigate be owned by these user/group.

Describe the solution you'd like
Allow the env variables PUID/PGID be specified.

Describe alternatives you've considered
Maybe specify the user/group in the Frigate config file?

Additional context
The root folder I am using for files for Frigate uses ACL so I can't just write files as root.

EDIT: Seems like the s6 tool you're using can drop privileges: https://github.com/just-containers/s6-overlay#dropping-privileges

@mikegleasonjr mikegleasonjr added the enhancement New feature or request label Jul 6, 2022
@PeteBa
Copy link

PeteBa commented Jul 14, 2022

I'd like to second this request. My use case is to transcode frigate recordings in-situ from the camera's H265 format to H264 so I can playback via the web-ui. Unfortunately, root ownership and default file permissions make this a bit problematic. Maybe consider including a UMASK env parameter as well if you add PUID and PGID.

@stale
Copy link

stale bot commented Aug 14, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Aug 14, 2022
@mikegleasonjr
Copy link
Author

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

still relevant...

@stale stale bot removed the stale label Aug 14, 2022
@blakeblackshear
Copy link
Owner

Related to #3108

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request pinned
Projects
None yet
Development

No branches or pull requests

3 participants