I don’t know if I’m stupid or if NextCloud’s instructions are stupid, it’s probably me and subsequently I’m struggling.
For all of my Docker stuff, I move the config directory to my opt folder with a simple
volumes:
- /opt/APPNAME/config:/config
And generally have the data on a remote drive like
- music:/music
volumes:
music:
driver_opts:
type: "nfs"
o: "addr=192.168.X.XXX,nolock,soft,rw"
device: ":/mnt/HD/Public/Shared Music"
This works perfectly for everything and I’m generally pleased with how things run. But NextCloud is throwing a bunch of words at me and I don’t get it. Why can’t it be as simple as what I’m already doing? Why do I have to declare
environment
- NEXTCLOUD_DATADIR=
- NEXTCLOUD_MOUNT=
And why is it pointing me to? https://github.com/nextcloud/all-in-one?tab=readme-ov-file#how-to-store-the-filesinstallation-on-a-separate-drive
Which just points you to https://www.guguweb.com/2019/02/07/how-to-move-docker-data-directory-to-another-location-on-ubuntu/
I’m looking at this Docker Compose like…
NextCloudPi was so simple to set up. If not for being stuck on v25, I’d have been happy with it. 🥺
I believe the answer is that aio needs the core data to be in specifically named volumes.
Sorry, this may seem dumb, but what does that mean?
You moved the config for out of a docker volume and pointed it to a specific directory.
That what I would like to do
I’m rereading your post now and looking at the aio compose file and I’m trying to figure out what exactly you changed.
If you’re using aio I don’t even see a config volume for you to have altered.
https://github.com/nextcloud/all-in-one/blob/main/compose.yaml
The only thing I changed was the environment section and the ports
ports: - 6001:80 - 6002:443 - 6003:4443 environment: - AIO_DIABLE_BACKUP_SECTION=true - NEXTCLOUD_DATADIR=/opt/nextcloudI don’t think you can move the configs with aio. At least I can’t see a way to do it.
There’s multiple containers that all need their own separate volumes, none of which are defined in that docker compose, because it’s handled programmatically by the master container. That’s why it directs you to moving where docker stores it’s volumes, if you want to move it all.
That’s the trade-off with using aio instead of running and configuring each docker container on your own.
Ah, that’s why. Thank you so much for explaining it!