Allow to start mastercontainer in offline environment (no internet access)

[logan893]

Steps to reproduce

1. Disconnect your internet connectivity (or block outgoing external access from nextcloud in your firewall)
2. Restart nextcloud AIO server (or stop and start all docker containers)

Expected behavior

Nextcloud AIO admin interface should be accessible even when server's external internet connectivity is down during the nextcloud-aio-mastercontainer startup

Actual behavior

nextcloud-aio-mastercontainer startup is blocked (restart loop) when not able to access https://ghcr.io, preventing all browser-based maintenance including manual backup actions

Other information

Host OS

Not relevant

Output of sudo docker info

Not relevant

Docker run command or docker-compose file that you used

Not relevant

Other valuable info

Failure when local DNS cache can provide IP lookup to ghcr.io, but the https connectivity fails:

curl: (28) Failed to connect to ghcr.io port 443 after 130437 ms: Could not connect to server
Could not reach https://ghcr.io.
Most likely is something blocking access to it.
You should be able to fix this by following https://dockerlabs.collabnix.com/intermediate/networking/Configuring_DNS.html
Another solution is using https://github.com/nextcloud/all-in-one/tree/main/manual-install
See https://github.com/nextcloud/all-in-one/blob/main/manual-install/latest.yml

Failure when no DNS lookup is possible:

curl: (6) Could not resolve host: ghcr.io
Could not reach https://ghcr.io.
Most likely is something blocking access to it.
You should be able to fix this by following https://dockerlabs.collabnix.com/intermediate/networking/Configuring_DNS.html
Another solution is using https://github.com/nextcloud/all-in-one/tree/main/manual-install
See https://github.com/nextcloud/all-in-one/blob/main/manual-install/latest.yml

[szaimen]

Hi, the thing is that AIO does not support running in an airgapped or offline environment. That is why we block it from starting in such an environment. See https://github.com/nextcloud/all-in-one?tab=readme-ov-file#can-i-run-aio-offline-or-in-an-airgapped-system

[szaimen]

However the check only happens on first startup. If the container already runs before internet goes down and you dont restart it afterwards, you should still be able to access it.

[szaimen]

Of course there might be unexpected problems coming up since as I said it does not officially support such environments.

[logan893]

This is either concerning or a bit absurd - perhaps both.

What are the know side-effects of having AIO running (post-install) while your external internet connectivity is down?
Do automatic backups still function in case the mastercontainer is unable to start?

If it is a problem/concern, would you suggest to have some internet service (ghcr.io reachability) monitor that restarts the mastercontainer, essentially putting it into this "safe" startup loop until internet service is restored?