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/nextcloud
I 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!
nextcloud
Nextcloud is a suite of client-server software for creating and using file hosting services.
IRC: #nextcloud on libera.chat
Matrix: #nextcloud:matrix.org
Other Nextcloud communities on Lemmy