szaimen

Hi @comet424 , have you checked the official install docs for unraid? https://github.com/nextcloud/all-in-one?tab=readme-ov-file#how-to-run-aio-on-unraid

Hi, see https://github.com/nextcloud/all-in-one?tab=readme-ov-file#how-to-properly-reset-the-instance

Hi, see https://github.com/nextcloud/all-in-one?tab=readme-ov-file#how-to-allow-the-nextcloud-container-to-access-directories-on-the-host

Hi, see https://github.com/nextcloud/all-in-one?tab=readme-ov-file#how-to-adjust-the-php-memory-limit-for-nextcloud

When I understand you old config correctly, you most likely need to rsync the data in /mnt/user/appdata/nextcloudaio/ to /var/lib/docker/volumes/nextcloud_aio_mastercontainer/_data/ and recreate the mastercontainer with the correct command which should make things work.

Hi, see https://help.nextcloud.com/t/nextcloud-aio-mastercontainer-missing/159268/2 and below

Hi, see https://github.com/nextcloud/all-in-one#how-to-run-nextcloud-behind-a-cloudflare-tunnel for how to run AIO behind a Cloudflare Tunnel

Hi, you cannot change it to not use volumes for data to be stored apart from Nextclouds datadir and the location of backups. However feel free to move the docker.img file that stores all docker related data to a different location that is covered by raid or similar.

The reason is that the data must be located in the correct volume because otherwise the built-in backup solution won't work. However feel free to move the docker image file that stores all docker related data to a different location that is covered by raid or similar.

Please change -v /mnt/user/appdata/nextcloud-aio:/mnt/docker-aio-config:rw to -v nextcloud_aio_mastercontainer:/mnt/docker-aio-config:rw which will make it work. So obviously you did not follow https://myunraid-ru.translate.goog/nextcloud-aio/?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=de&_x_tr_pto=wapp step-for-step.

Can you post the output of sudo docker inspect nextcloud-aio-mastercontainer here?

Yes, see this guide: https://myunraid-ru.translate.goog/nextcloud-aio/?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=de&_x_tr_pto=wapp

Hi, see https://github.com/nextcloud/all-in-one#how-to-properly-reset-the-instance

Cool! No idea, sorry. Maybw unraid changes things back?

Hi, is this the complete log? Also here you find how you need to adjust the permissions to make it work: https://myunraid-ru.translate.goog/nextcloud-aio/?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=de&_x_tr_pto=wapp

Solved in https://github.com/nextcloud/all-in-one/discussions/1885

Yes, AIO is official. Correct.

Hi, this issue is a general Linux permissions issue and has nothing to do specifically with AIO. You should be able to fix the problem with an additional `chown -R 33:0 /mnt/user/Nextcloud`

Hi, it seems like a few aio containers are still running. You can find them with `sudo docker ps | grep nextcloud-aio`. They need to be stopped and afterwars cleaned by following https://github.com/nextcloud/all-in-one. Afterwards you can try again.

Hi, you need to change the acl permissions of the smb share where your files are located on to 0770 instead of 0777.

This is what is not supported. It must be "nextcloud_aio_mastercontainer:/mnt/docker-aio-config:rw" but please try again after resetting properly.

Hi, so it looks like based on the log that you provided that something indeed failed on you. Can you try again after resetting things properly https://github.com/nextcloud/all-in-one#how-to-properly-reset-the-instance?

Hi, can you post the output of `sudo docker inspect nextcloud-aio-mastercontainer` here?

Yes, in the screenshot are you using `30:0` instead of `33:0`. Do you see the difference?

Hi, I think the chown command is wrong. It should be `chown -R 33:0 /mnt/user/slownas` afaik. Cheers!