TLDR: I consistently fail to set up Nextcloud on Docker. Halp pls?
Hi all - please help out a fellow self-hoster, if you have experience with Nextcloud. I have tried several approaches but I fail at various steps. Rather than describe my woes, I hope that I could get a “known good” configuration from the community?
What I have:
- a homelab server and a NAS, wired to a dedicated switch using priority ports.
- the server is running Linux, Docker, and NPM proxy which takes care of domains and SSL certs.
What I want:
- a
docker-compose.ymlthat sets up Nextcloud without SSL. Just that. - ideally but optionally, the compose file might include Nextcloud office-components and other neat additions that you have found useful.
Your comments, ideas, and other input will be much appreciated!!
You must log in or register to comment.
FYI docker images binding to an NFS mount can be tricky due to ACL extensions not being supported. Podman is especially bad for this.
Their official image is easy to run, just one container needed: https://hub.docker.com/_/nextcloud
Linuxserver.io images are also good: https://hub.docker.com/r/linuxserver/nextcloud
It all comes down to which webserver you want to use actually
Base official image and linuxserver.Io comes with Apache
With fpm you can choose
+1 for the linuxserver.io container. It is easier to use than anything else I’ve found.
Nextcloud is very easy to setup as a container. You just need a MySQL/MariaDB server and a volume mount. Just make sure the volume is owned by www-data user (uid:gid 33:33). That’s it. Most problems I’ve seen so far are related to files permissions, so double check to make sure the volume is owned by www-data.
is marinade a typo for mariadb or is this some new thing that i missed
I swear I already double checked but Gboard’s autocorrect always managed to mess up something
