[Enhancement]: make a docker-compose.yml

[l3m]

This would allow users to upgrade the Nextcloud docker container (to a newer version) while keeping all data.

[nrgeen]

It's already working. In my installation it works with the following preferences very well:

-v /volume/nextcloud_docker/config:/usr/share/webapps/nextcloud/config
-v /volume/nextcloud/apps:/usr/share/webapps/nextcloud/apps 
-v /volume/nextcloud/data:/usr/share/webapps/nextcloud/data
-v /volume/nextcloud/sslCert:/root/sslKeys

[l3m]

Sure. But ideally, this would be preconfigured in a docker-compose.yml. I guess most people finding this repo will just start the service, and then have an unhappy surprise when after an update, all their data is gone.

I think it should at least mention that additional work is needed to make it useful in the longer term, if not providing data volumes or mapped directories as default.

Also, please don't misunderstand - I am very grateful for you to provide this dockerized nextcloud. Thanks for your work!

[greyltc]

I'm not so familiar with docker-compose, I'd be super happy to have help in forming the yml file.
PRs welcome!

[l3m]

A nice example can be found here, for Mattermost:

https://github.com/mattermost/mattermost-docker

[greyltc]

Great, can you modify that for this project and present it here?

[l3m]

If I had the time to do this with proper testing, you would have the prq already - sigh. Maybe this weekend....

[Calprainn]

I also linked the -v parameters with my local storage, in my docker create command, but I get a access/permission failure after I start the Nextcloud setup. Either Nextcloud can't access the data folder (because the chmod setting is wrong) or “all users can access" (after I setting chmod to 777, for testing) and Nextcloud won't continue.

What are the permission rights (chmod) for the folders (/config, /data, /apps) and what's the user/group?

[greysAcademicCode]

Yeah, managing the permissions on various files that nextcloud touches is tricky, especially when volume mapping all over everything in a docker container.

Here is the section of the nextcloud manual that covers the permissions that it expects:
https://docs.nextcloud.org/server/9/admin_manual/installation/installation_wizard.html#strong-perms-label

I've written a script that (re)sets these permissions:
https://aur.archlinux.org/cgit/aur.git/tree/set-nc-perms.sh?h=nextcloud

You can run 'set-nc-perms runtime' in the container. That might fix everything.

[Calprainn]

Thanks for your advice.
I've run your command and I think it worked. The permission error message has no longer appears.

But now, when I logged in Nextcloud, Safari (or Chrome) says: ERR_TOO_MANY_REDIRECTS. (on address: “https://my.local.server/nextcloud/index.php/apps/files/“). When I access “https://my.local.server/nextcloud/index.php/settings/personal“ directly, for example, the page show up.

I think there is still a problem with the /data/ folder permissions?!

//edit
I removed my Nextcloud container and rebuild a new one to have a clean "install".
Nextcloud Login page -> login /w user and pass -> same browser error - too many redirects. :(

[samnazarko]

+1 for storing data and config out of the docker image.

[kmain4]

@Calprainn How did you resolve that?