Nextcloud Start via Script (StartContainers.php) ignores custom networks configured in the AIO

[Asterdux1]

Steps to reproduce

1. Start the nextcloud mastercontainer
2. Boot up the nextcloud using docker exec -it nextcloud-aio-mastercontainer sudo -u www-data php /var/www/docker-aio/php/src/Cron/StartContainers.php or docker exec -it nextcloud-aio-mastercontainer sudo -u www-data php /var/www/docker-aio/php/src/Cron/StartAndUpdateContainers.php
3. Done

Expected behavior

Spawned Nextcloud Apache Container should have docker network I defined in Environment Variables attached. (APACHE_ADDITIONAL_NETWORK: name_of_network).

Actual behavior

Spawned apache container is not attached to the name_of_network network, and therefore proxies like traefik can no longer forward traffic.

Other information

Tested across docker compose, docker run, ubuntu 24.04 and arch rolling.
Is not an issue on my side.
Network option works fine when starting nextcloud via the web ui, however not through automation.

[Asterdux1]

I see this has turned into a discussion, does that mean it was not recognized as a bug?

[szaimen]

Hi, see https://github.com/nextcloud/all-in-one#how-to-stopstartupdate-containers-or-trigger-the-daily-backup-from-a-script-externally