From 94509ab3eafdfa9e6b060aba3fff963d191e0d93 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lukas=20M=C3=BCller?= Date: Wed, 13 Dec 2023 22:26:56 +0100 Subject: [PATCH] Disrecommend to use CIFS/SMB shares as datadir MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Lukas Müller --- readme.md | 15 ++------------- 1 file changed, 2 insertions(+), 13 deletions(-) diff --git a/readme.md b/readme.md index fe660d59cc3..41f3ccf42f5 100644 --- a/readme.md +++ b/readme.md @@ -591,20 +591,9 @@ You can configure the Nextcloud container to use a specific directory on your ho ### Can I use a CIFS/SMB share as Nextcloud's datadir? -Sure. Add this to the `/etc/fstab` file:
-` cifs rw,mfsymlinks,seal,credentials=,uid=33,gid=0,file_mode=0770,dir_mode=0770 0 0`
-(Of course you need to modify ``, `` and `` for your specific case.) +This is not recommended. -One example could look like this:
-`//your-storage-host/subpath /mnt/storagebox cifs rw,mfsymlinks,seal,credentials=/etc/storage-credentials,uid=33,gid=0,file_mode=0770,dir_mode=0770 0 0`
-and add into `/etc/storage-credentials`: -``` -username= -password= -``` -(Of course you need to modify `` and `` for your specific case.) - -Now you can use `/mnt/storagebox` as Nextcloud's datadir like described in the section above above this one. +There is a bug in one of the upstream dependencies that likely will not be fixed anytime soon. This bug prevents uploading large files and deleting directories containing a large number of files (>62 files). See https://github.com/nextcloud/all-in-one/discussions/2850#discussioncomment-6269418, https://github.com/nextcloud/server/issues/17980 and https://gitlab.alpinelinux.org/alpine/aports/-/issues/10960 for details. ### How to allow the Nextcloud container to access directories on the host? By default, the Nextcloud container is confined and cannot access directories on the host OS. You might want to change this when you are planning to use local external storage in Nextcloud to store some files outside the data directory and can do so by adding the environmental variable `NEXTCLOUD_MOUNT` to the docker run command of the mastercontainer (but before the last line `nextcloud/all-in-one:latest`! If it was started already, you will need to stop the mastercontainer, remove it (no data will be lost) and recreate it using the docker run command that you initially used). Allowed values for that variable are strings that start with `/` and are not equal to `/`.