Sorry to be not clear enough. The question is not if the compose.yaml is wrong or that Nextcloud is not running. This is all fine. The question is, how to force an update of the configuration if I make some changes regarding the environment variables in the compose.yaml.
$ sudo docker stop nextcloud-aio-mastercontainer $ sudo docker compose up -d # detach [+] Building 0.0s (0/0) WARN[0000] volume “nextcloud_aio_mastercontainer” already exists but was not created by Docker Compose. Use external: true to use an existing volume [+] Running 1/1 ✔ Container nextcloud-aio-mastercontainer Started
I also managed to access the Nextcloud AIO v11.11.0 web interface (this is a little bit complicated in my network) and re-started. Now I can see the local storage.