Nextcloud asking to change the permissions to 0770 on a directory

cd to wherever your data directory is

sudo chmod 0770 directory_name

Zitat von pi_projects

So I ran sudo docker exec -it <docker-container name> /bin/bash

And found the data directory and applied chmod 0770 data/

But then I got a new error, and it seems to be a lot worse than the previous error.

Did you listen to a word I said? It is worse because you didn't do as I said.

I would probably just start over in this case or do a lot of reading on how those permissions are set.

Zitat von pi_projects

You told me to cd and find the directory where the data folder is stored which I did. You then said to use the following command sudo chmod 0770 directory_name, which I also did. At what point did I not listen to what you said when I did the only 2 things you advised me to do? That new error came about as soon as I applied that specific change.

I'll just delete the old containers and build it again and see what happens. Hopefully, that just fixes things.

No, you bashed into the container and ran the command... that is why the error changed. The /data folder is mapped in your docker-compose.

volumes:
      - /path/to/appdata:/config
      - /path/to/data:/data

Whatever you listed to the left of :/data in your docker-compose.yml is your data folder

Zitat von pi_projects

So I did a fresh install and it was working for a few days, then I got the same error again but this time I went to the path located in the docker-compose file and did "sudo chmod 0770 Data". But I still got the same error.

What went wrong this time?

I deployed the container again and it works fine, but out of nowhere I keep getting the error that tells me to make the data directory 0770. How do I stop that from happening?

Well the fact it has happened to you a second time, it's clearly something you are doing.

Post your docker-compose/stack file you're using.

How are you creating the directories involved? (Particularly the folders maapped to /data). It's strange this is working for a few days before it goes fubar.

Zitat von pi_projects

Code

version: '2'

services:
  db:
    image: yobasystems/alpine-mariadb:latest
    command: --transaction-isolation=READ-COMMITTED --binlog-format=ROW
    restart: always
    volumes:
      - /srv/dev-disk-by-uuid-b547c458-72ff-4fc3-a4d0-65940dde8b0d/Database/NextCloud:/var/lib/mysql
    environment:
      - MYSQL_ROOT_PASSWORD=
      - MYSQL_PASSWORD=
      - MYSQL_DATABASE=
      - MYSQL_USER=

  app:
    image: nextcloud
    ports:
      - 8080:80
    links:
      - db
    volumes:
      - /srv/dev-disk-by-uuid-b547c458-72ff-4fc3-a4d0-65940dde8b0d/Config/Nextcloud:/var/www/html
    restart: always

Alles anzeigen

I was following a Youtube tutorial that walked through the set up here's the link

I'm new to this so maybe I have completely missed something that's causing an issue.

Is there any particular reason you didn't just follow the official instructions here on the forum?

Zitat von pi_projects

Not really, every other tutorial worked well for me so I just assumed the nextcloud one will work with no problems since it was easy to follow.

So I found this on a guide but I removed the SWAG part since I don't need that. Would I have any issues running this?

Code

version: "2"
services:
  nextcloud:
    image: ghcr.io/linuxserver/nextcloud
    container_name: nextcloud
    environment:
      - PUID=1000 #change PUID if needed
      - PGID=100  #change PGID if needed
      - TZ=Europe/Berlin #change Time Zone if needed
    volumes:
      - /srv/dev-disk-by-label-disk1/appdata/nextcloud/config:/config #/srv/dev-disk-by-label-disk1 needs to be adjusted
      - /srv/dev-disk-by-label-disk1/appdata/nextcloud/data:/data     #/srv/dev-disk-by-label-disk1 needs to be adjusted
    depends_on:
      - mariadb
#    ports: # uncomment this and the next line if you want to bypass the proxy
#      - 450:443
    restart: unless-stopped
  mariadb:
    image: ghcr.io/linuxserver/mariadb
    container_name: nextclouddb
    environment:
      - PUID=1000 #change PUID if needed
      - PGID=100  #change PGID if needed
      - MYSQL_ROOT_PASSWORD=mariadbpassword  #change password
      - TZ=Europe/Berlin #Change Time Zone if needed
    volumes:
      - /srv/dev-disk-by-label-disk1/appdata/nextclouddb:/config    #/srv/dev-disk-by-label-disk1 needs to be adjusted
    restart: unless-stopped

Alles anzeigen

Although it seems a little weird to have Nextcloud w/o external access... That should work fine if you don't intend to use swag... Just make sure you adjust the necessary lines indicated (passwords, PUID/PGID's, etc.)..

And just to get it out of the way since you're apparently watching dbtech videos... DO NOT USE PUID 998

Zitat von pi_projects

Yeah, I'm just creating this to be used on my local network, I want to just the hang of things before I start opening up to remote access etc. I know it can be dangerous to start opening things up to the internet without proper understanding.

And I didn't use PUID 998 in the docker-compose file, unless you mean that's what it defaults to if not specified?

I'll start looking at the guides here since you're saying they're better supported.

No.. you need to make sure you have a user on your server assigned to PUID (1000 is the first user created, if you've created one)..

The 998 thing is something dbtech does that causes a lot of people permission problems w/ some containers and we have to discuss it frequently here.