unRAID Docker Compose #4602
-
I've been attempting to convert from Nextcloud to Nextcloud AIO using docker compose on Unraid. I setup everything per the sprinkled aforementioned unRAID instructions and created my docker-compose file. However upon stopping the stack, I'm noticing plenty of Nextcloud all in one containers lingering around in a stopped mode. After a reboot of my test server and attempting to start the compose stack, I am unable to access my Nextcloud as previously running on my Any suggestions or reasons why this is occurring? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi, the reason is that you always have to stop the containers via the aio interface on port 8080. Apart from that see https://github.com/nextcloud/all-in-one?tab=readme-ov-file#how-to-stopstartupdate-containers-or-trigger-the-daily-backup-from-a-script-externally |
Beta Was this translation helpful? Give feedback.
Hi, the reason is that you always have to stop the containers via the aio interface on port 8080. Apart from that see https://github.com/nextcloud/all-in-one?tab=readme-ov-file#how-to-stopstartupdate-containers-or-trigger-the-daily-backup-from-a-script-externally