Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
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

Permissions #22

Closed
hackmonker opened this issue Jun 16, 2022 · 5 comments
Closed

Permissions #22

hackmonker opened this issue Jun 16, 2022 · 5 comments
Assignees
Labels
help wanted Extra attention is needed

Comments

@hackmonker
Copy link

Was facing a bit problem regarding the downloads permissions. all the downloaded files seem to be having root:root permissions. any way we can use my user for it? I tried setting puid and guid but it still gives the downloaded files root ownership. is it not possible or am I missing something?

@antlafarge
Copy link
Owner

antlafarge commented Jun 20, 2022

Hello, you should give ownership on these folders to your user. If you let Docker create these directories for you, the root will have the ownership (as user and as group) on these directories. Look at chown command.
And check the uid and gid are correct :)

@domi-a
Copy link

domi-a commented Jun 22, 2022

Hello, you should give ownership on these folders to your user. If you let Docker create these directories for you, the root will have the ownership (as user and as group) on these directories. Look at chown command. And check the uid and gid are correct :)

i was facing the same issue. this works for me.
had to set rights of the _data folder in the generated config volume and the downloads folder to my user along with user:1000:100 on raspberry-os

@antlafarge
Copy link
Owner

Thank you for this information, I will add this information in the README to clarify this step.

@domi-a
Copy link

domi-a commented Jun 22, 2022

04fba1c

you can even do it with volumes created by docker or docker-compose.

  • it will fail at first start after volume creating because of the root rights in the config volume
  • but then i changed the permissions of the _data folder in the created config volume
  • restartet the container and it worked like a charm.

@antlafarge
Copy link
Owner

antlafarge commented Jun 22, 2022

For sure, but having a process where a failure is a normal path is not a great idea in my opinion.
So I prefer to explain to users they need to create the folder before.

@antlafarge antlafarge self-assigned this Jul 22, 2022
@antlafarge antlafarge added the help wanted Extra attention is needed label Jul 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants