Hey @szaimen are there any new informations here? I am having the exact same issue. My master container doesnt start the other containers. Shouldnt it do that?
Sorry for the late reply. The issue is, that the master container is set to autostart in unraid, but the master container doesnt start all the other containers. I have to manually access the aio-webui and start all containers from there.
Here only the mastercontainer is set to autostart. The others arent. Also i cant just set them to autostart, as it seems like, they have a specific order in which they autostart, which i havent figured out yet. It would be easier, if there was an option for the mastercontainer to start the child-containers with it. The master container has ro rights on the docker socket, so should be doable.
Wouldnt it be possible to have an environment variable to configure, so the mastercontainer autostarts (or maybe updates and autostarts) all the child containers, just in case someone is not able to easily configure the autostart like on unraid, there still would be the variable
In my opinion, there should be an official simple way to do this. I know alot of people who use unraid with nextcloud-aio and they all face this problem.
I am wondering how is unraid storing this config flag to autostart the container? Is it stored in a custom database inside the docker management tool or somewhere else like e.g. as a label for the container? Without this information we cannot do anything in AIO.
I fear there is no way then for AIO to automatically configure this for you and also no manual way for AIO since unraids implementation is done in this way. So you need to enable this flag manually via this unraid interface for all containers.