Docker + Nextcloud = why is it so difficult?
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 are viewing a single comment
As others have commented, Nextcloud provide an all-in-one docker set up. I managed to follow the instructions and get it working.
However, in the end, I wanted this to replace my Dropbox subscription, and my files and reliable access to them are important to me. Given that, and my relatively low skill level, I didn't want to futz with troubleshooting failed updates and server issues, so I just went with a Hetzner storage share, which is their managed nextcloud subscription: https://www.hetzner.com/storage/storage-share
This is a completely valid option and one that more people should consider. You don't have to selfhosted everything, even if you can. I actually prefer to support existing instances of stuff in a lot of cases.
I use https://disroot.org for email and cloud, and I'm more than happy to kick them a hundred bucks a year to help support a community. Same with https://fosstodon.org for Mastodon. I'm fully capable of self-hosting these things, but instead I actively choose to support them instead so that their services can be extended to more than just myself. I chose those two because they send excess funds upstream to FOSS projects. I'm proud to rep those domains.
I found the AIO to be kind of quirky in the way it's architected, including having a master container that must be named exactly and I couldn't find a way to make a bind mount for the config/data (that part was a deal breaker). Probably up their with LSIO in simplicity, however, and it doesn't default to sqlite which is nice.