Selfhosted

39939 readers

364 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Another permission question (lemm.ee)

submitted 11 months ago by atek@lemm.ee to c/selfhosted@lemmy.world

13 comments fedilink hide all child comments

Hi,

I'm trying my best to setup Nextcloud on my mediaserver, but I cannot work out the permissions to my data folder.

My setup is as follows: proxmox server openmediavault VM with 8tb disk and nfs shares debian mediaserver with docker compose (including nextcloud docker)

the nfs share is set to 775. I linked it in my debian server through /etc/fstab. I can write to the folder without a problem.

In my docker compose file i linked /mnt/photos:/photos to the nextcloud container. When i login to my container i cannot write files to the folder.

When i change the share to 777, i can write files, but nextcloud setup stops and says my permissions are wide open, so it won't continue the setup.

I turn it back to other:read/execute and the container cannot write to the folder anymore.

What am i doing wrong?

you are viewing a single comment's thread
view the rest of the comments

[–] atzanteol@sh.itjust.works 4 points 11 months ago (5 children)

Nextcloud uses the www-data user internally. Id is 33. You should be able to "chown 33 dirname" on the nfs server. That may work?

[–] atek@lemm.ee 1 points 11 months ago (1 children)

I want to try that, but i've got to add: i want to access this folder from my desktop too. i added it the same way in /etc/fstab and it worked instantly

[–] atzanteol@sh.itjust.works 4 points 11 months ago* (last edited 11 months ago) (1 children)

That's what group permissions are for. You can add yourself to the www-data group and chown www-data:www-data path. Then you and the container should be able to operate on the contents.

[–] med@sh.itjust.works 2 points 11 months ago (1 children)

Do not forget to log out and log back in after you add yourself to a new group. Your desktop environment is a program, and it won’t know about the update until you spawn a new graphical shell with the updated permissions.

[–] SheeEttin@lemmy.world 2 points 11 months ago

Or just start a new login shell.

load more comments (3 replies)