7
Another permission question (lemm.ee)
submitted 2 years ago by 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?

all 14 comments

sorted by: hot top controversial new old
[–] 4 points 2 years ago (2 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?

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 1 point 2 years ago (1 child)

    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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 2 years ago* (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
    • [–] 1 point 2 years ago* (1 child)

    You need to allow nextcloud to control the file permissions. You can do this with the no_root_squash option in the /etc config file

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
    • [–] 0 points 2 years 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?

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] [S] 1 point 2 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago* (1 child)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 2 years ago (1 child)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years 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.

  • permalink
  • fedilink
  • source
  • parent