Stuck on "start and update containers" in mainland China

[horsley]

docker run   --rm   --init   --sig-proxy=false  \
>  --name nextcloud-aio-mastercontainer  \
>   --volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config  \
>     --volume /var/run/docker.sock:/var/run/docker.sock:ro \
>      -e DOCKER_API_VERSION=1.41 \
>      -e APACHE_PORT=11000 \
>      --network=dokploy-network \
>      ghcr.io/nextcloud-releases/all-in-one:latest
Trying to fix docker.sock permissions internally...
Creating docker group internally with id 991
DOCKER_API_VERSION was found to be set to '1.41'.
Please note that only v1.44 is officially supported and tested by the maintainers of Nextcloud AIO.
So you run on your own risk and things might break without warning.
Initial startup of Nextcloud All-in-One complete!
You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
E.g. https://internal.ip.of.this.server:8080
⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!

If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
https://your-domain-that-points-to-this-server.tld:8443
/usr/lib/python3.12/site-packages/supervisor/options.py:13: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.
  import pkg_resources
++ head -1 /mnt/docker-aio-config/data/daily_backup_time
+ BACKUP_TIME=20:00
+ export BACKUP_TIME
+ export DAILY_BACKUP=1
+ DAILY_BACKUP=1
++ sed -n 2p /mnt/docker-aio-config/data/daily_backup_time
+ '[' '' '!=' automaticUpdatesAreNotEnabled ']'
+ export AUTOMATIC_UPDATES=1
+ AUTOMATIC_UPDATES=1
++ sed -n 3p /mnt/docker-aio-config/data/daily_backup_time
+ '[' successNotificationsAreNotEnabled '!=' successNotificationsAreNotEnabled ']'
+ export SEND_SUCCESS_NOTIFICATIONS=0
+ SEND_SUCCESS_NOTIFICATIONS=0
+ set +x
[21-Dec-2025 07:39:09] NOTICE: fpm is running, pid 149
[21-Dec-2025 07:39:09] NOTICE: ready to handle connections
[Sun Dec 21 07:39:09.258951 2025] [mpm_event:notice] [pid 144:tid 144] AH00489: Apache/2.4.66 (Unix) OpenSSL/3.5.4 configured -- resuming normal operations
[Sun Dec 21 07:39:09.258998 2025] [core:notice] [pid 144:tid 144] AH00094: Command line: 'httpd -D FOREGROUND'
{"level":"info","ts":1766302749.2637177,"msg":"maxprocs: Leaving GOMAXPROCS=4: CPU quota undefined"}
{"level":"info","ts":1766302749.2642505,"msg":"GOMEMLIMIT is updated","package":"github.com/KimMachineGun/automemlimit/memlimit","GOMEMLIMIT":3575697408,"previous":9223372036854775807}
{"level":"info","ts":1766302749.264316,"msg":"using config from file","file":"/Caddyfile"}
{"level":"info","ts":1766302749.2665324,"msg":"adapted config to JSON","adapter":"caddyfile"}
{"level":"info","ts":1766302749.268708,"msg":"serving initial configuration"}

Infinite loading on aio web interface and no extra log after click the button, I can't found any log level setting of master container, what was the master container doing there?

[horsley]

After some investigation by code reading and docker sock sniff, I found that it's stucked at image update.
ghcr.io download speed lower than 100kb/s on tencent cloud lighthouse machine with 5Mbps bandwidth. The image was quite big, pulling was stuck also by manual operation, plenty kb progress in several seconds.
I try to save image from another machine and load, it works.

Nextcloud AIO try to handle all the docker operations in one place, then all related problems like #3977 should be considerated, some way to use mirror, proxy, etc.

[horsley]

There was so many mirrors for dockerhub but not for ghcr.io, :(

[horsley]

The container nextcloud-aio-nextcloud using php alpine for base image. Which stuck at "Enabling Imagick..." quite long.
There also many mirrors for os software source like the mirror of cloud service itself, it's extremely fast because using internal networking which not limited by internet bandwidth. It's could be better for AIO to leave some customization mechanism for users to do small tweaks like this but not install all components manually

[szaimen]

Hi, we have an improvement for this here: #7335

[szaimen]

This is now released with v12.4.0 Beta. Testing and feedback is welcome! See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel

[leoniscsem]

In my humble opinion this is a pointless endeavour, as I am located in mainland China as well and have dealt with the countless issues caused by the GFW. Whenever you need to pull something from either Docker repos or GitHub repos, your processes will be slowed down gradually. This most likely has nothing to do with Nextcloud AiO but with the decisions of complete morons Our Glorious Leaders.
Get a cheap Aliyun/Tencent HK server for SSH tunneling / SOCKS5. I have faced these issues for many years, not only with our own infrastructure but with client infrastructure as well. At one point I simply gave up. Do not tunnel the application itself through the SOCKS5, as this will likely result in your HK IP being auto-banned by the GFW, but tunnel ALL your network traffic through that via SSH, then update, then close the tunnel again.

Another, new issue related to the problem: Chinese IP ranges, also those in HK (Aliyun, Tencent, Hicloud), are getting banned steadily by various repository providers due to bad practices of AI scraping.