this post was submitted on 20 Nov 2023
7 points (81.8% liked)

Selfhosted

39939 readers
368 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
7
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
[–] ninjan@lemmy.mildgrim.com 0 points 11 months ago (2 children)

Try telling Docker its rw explicitly:

  • /mnt/photos:/photos:rw

It should be rw by default but I can't see what else could be happening. What account runs docker? What account runs nextcloud inside the container?

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

how can i check which accounts are used? I think my normal user account sets up docker, with uid & gid = 1000. I don't think i created an account in the container so probably root.

[–] JASN_DE@feddit.de 1 points 11 months ago* (last edited 11 months ago) (1 children)

The official NC docker container uses the "www-data" internally to run the services. This will get important if you ever want to run tasks via "docker compose exec".

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

When I run: docker exec -it nextcloud bash I get: root@nextcloud:/var/www/html#, does this mean it uses www?

[–] tvcvt@lemmy.ml 1 points 11 months ago

From that prompt, type ls -l. That will show you a listing of the items in the /var/www/html directory and there will be columns for the user and group that own each file. It will most likely say www-data.

[–] possiblylinux127@lemmy.zip 1 points 11 months ago

That won't fix it because its a permission issue at the NFS level