Nextcloud-aio-mastercontainer stuck in restarting loop?

KeithGP · June 28, 2023, 10:07pm

Nextcloud version (eg, 20.0.5): 25.0.4.1 AIO
Operating system and version (eg, Ubuntu 20.04): Windows 10
Apache or nginx version (eg, Apache 2.4.25): replace me
PHP version (eg, 7.4): replace me

The issue you are facing:

I have been running Nextcloud AIO through Docker Desktop on Windows 10 for about 2 months without issue. Upgraded Docker for the 3rd time and did not think anything of it. I noticed on my smartphone that I could no longer backup.

nextcloud-aio-mastercontainer stuck in restarting loop inside Docker Desktop 4.20.1

Is this the first time you’ve seen this error? (Y/N): YES

Steps to replicate it:

Updated Docker Desktop to 4.20.1
Restarted Windows 10
Never able to start Nextcloud again

The output of your Nextcloud log in Admin > Logging:

2023-05-19 23:57:55 Trying to fix docker.sock permissions internally...
2023-05-19 23:57:55 Adding internal www-data to group root
2023-05-19 23:57:56 WARNING: No blkio throttle.read_bps_device support
2023-05-19 23:57:56 WARNING: No blkio throttle.write_bps_device support
2023-05-19 23:57:56 WARNING: No blkio throttle.read_iops_device support
2023-05-19 23:57:56 WARNING: No blkio throttle.write_iops_device support
2023-05-19 23:58:00 {"level":"info","ts":1684558680.990622,"msg":"using provided configuration","config_file":"/Caddyfile","config_adapter":""}
2023-05-19 23:58:00 {"level":"info","ts":1684558680.995948,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details."}
2023-05-19 23:58:01 [20-May-2023 04:58:01] NOTICE: fpm is running, pid 130
2023-05-19 23:58:01 [20-May-2023 04:58:01] NOTICE: ready to handle connections
2023-05-19 23:57:58 Initial startup of Nextcloud All-in-One complete!
2023-05-19 23:57:58 You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
2023-05-19 23:57:58 E.g. https://internal.ip.of.this.server:8080
2023-05-19 23:57:58 
2023-05-19 23:57:58 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:
2023-05-19 23:57:58 https://your-domain-that-points-to-this-server.tld:8443
2023-05-20 23:00:06 Deleted Images:
2023-05-20 23:00:06 untagged: nextcloud/aio-watchtower@sha256:1d625fe4b39832cba7aeb7d8facb9a94cadd2969930a362184a69a947f4920bb
2023-05-20 23:00:06 deleted: sha256:9244b493948affa46e25d04c3d65c0474af62146cd3f140f3830dc781caf0b25
2023-05-20 23:00:06 deleted: sha256:af22caba74f8adeb8de9bf50dc0daa4b1a2cc023d4c369d45b45f59b74c7baf9
2023-05-20 23:00:06 deleted: sha256:47fa70783c4a4d91abfacd9646b7de8618f14c76376ea52d9f6bcf89f7e2618e
2023-05-20 23:00:06 deleted: sha256:b06f99db777c17707e7ad225b8e72557421f85fb673ffbe8c3d214e843eabfb1
2023-05-20 23:00:06 deleted: sha256:6167debc6f7d66e391d7a719448a29507965aeb09bde52d3e16c373d9d4a5d78
2023-05-20 23:00:06 
2023-05-20 23:00:06 Total reclaimed space: 15.55MB
2023-05-21 23:00:12 Total reclaimed space: 0B
2023-05-22 23:00:18 Total reclaimed space: 0B
2023-05-23 23:00:25 Total reclaimed space: 0B
2023-05-24 23:00:01 Total reclaimed space: 0B
2023-05-25 23:00:07 Total reclaimed space: 0B
2023-05-26 14:17:47 Initial startup of Nextcloud All-in-One complete!
2023-05-26 14:17:47 You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
2023-05-26 14:17:47 E.g. https://internal.ip.of.this.server:8080
2023-05-26 14:17:47 
2023-05-26 14:17:47 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:
2023-05-26 14:17:47 https://your-domain-that-points-to-this-server.tld:8443
2023-05-26 14:17:45 WARNING: No blkio throttle.read_bps_device support
2023-05-26 14:17:45 WARNING: No blkio throttle.write_bps_device support
2023-05-26 14:17:45 WARNING: No blkio throttle.read_iops_device support
2023-05-26 14:17:45 WARNING: No blkio throttle.write_iops_device support
2023-05-26 14:17:49 {"level":"info","ts":1685128669.9108634,"msg":"using provided configuration","config_file":"/Caddyfile","config_adapter":""}
2023-05-26 14:17:49 {"level":"info","ts":1685128669.9238334,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details."}
2023-05-26 14:17:49 [26-May-2023 19:17:49] NOTICE: fpm is running, pid 119
2023-05-26 14:17:49 [26-May-2023 19:17:49] NOTICE: ready to handle connections
2023-05-26 23:00:26 Total reclaimed space: 0B
2023-05-27 23:00:01 Total reclaimed space: 0B
2023-05-28 23:00:07 Total reclaimed space: 0B
2023-05-29 23:00:12 Total reclaimed space: 0B
2023-05-30 23:00:18 Total reclaimed space: 0B
2023-05-31 23:00:24 Total reclaimed space: 0B
2023-06-01 23:00:29 Total reclaimed space: 0B
2023-06-02 23:00:17 Total reclaimed space: 0B
2023-06-03 23:00:23 Total reclaimed space: 0B
2023-06-04 23:00:29 Total reclaimed space: 0B
2023-06-05 23:00:05 Total reclaimed space: 0B
2023-06-06 23:00:10 Total reclaimed space: 0B
2023-06-07 23:33:15 WARNING: No blkio throttle.read_bps_device support
2023-06-07 23:33:15 WARNING: No blkio throttle.write_bps_device support
2023-06-07 23:33:15 WARNING: No blkio throttle.read_iops_device support
2023-06-07 23:33:15 WARNING: No blkio throttle.write_iops_device support
2023-06-07 23:33:17 Initial startup of Nextcloud All-in-One complete!
2023-06-07 23:33:17 You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
2023-06-07 23:33:17 E.g. https://internal.ip.of.this.server:8080
2023-06-07 23:33:17 
2023-06-07 23:33:17 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:
2023-06-07 23:33:19 {"level":"info","ts":1686198799.9373202,"msg":"using provided configuration","config_file":"/Caddyfile","config_adapter":""}
2023-06-07 23:33:19 {"level":"info","ts":1686198799.951147,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details."}
2023-06-07 23:33:20 [08-Jun-2023 04:33:20] NOTICE: fpm is running, pid 121
2023-06-07 23:33:20 [08-Jun-2023 04:33:20] NOTICE: ready to handle connections
2023-06-18 17:48:37 WARNING: No blkio throttle.read_bps_device support
2023-06-18 17:48:37 WARNING: No blkio throttle.write_bps_device support
2023-06-18 17:48:37 WARNING: No blkio throttle.read_iops_device support
2023-06-07 23:33:17 https://your-domain-that-points-to-this-server.tld:8443
2023-06-08 23:00:26 Total reclaimed space: 0B
2023-06-09 23:00:16 Total reclaimed space: 0B
2023-06-10 23:00:21 Total reclaimed space: 0B
2023-06-11 23:00:26 Total reclaimed space: 0B
2023-06-12 23:00:02 Total reclaimed space: 0B
2023-06-13 23:00:08 Total reclaimed space: 0B
2023-06-14 23:00:14 Total reclaimed space: 0B
2023-06-15 23:00:20 Total reclaimed space: 0B
2023-06-16 23:00:32 Total reclaimed space: 0B
2023-06-17 23:00:08 Total reclaimed space: 0B
2023-06-18 17:48:39 Initial startup of Nextcloud All-in-One complete!
2023-06-18 17:48:37 WARNING: No blkio throttle.write_iops_device support
2023-06-18 17:48:41 {"level":"info","ts":1687128521.9374468,"msg":"using provided configuration","config_file":"/Caddyfile","config_adapter":""}
2023-06-18 17:48:41 {"level":"info","ts":1687128521.965725,"msg":"failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details."}
2023-06-18 17:48:42 [18-Jun-2023 22:48:42] NOTICE: fpm is running, pid 125
2023-06-18 17:48:42 [18-Jun-2023 22:48:42] NOTICE: ready to handle connections
2023-06-18 17:48:43 [18-Jun-2023 22:48:43] NOTICE: Terminating ...
2023-06-18 17:48:43 [18-Jun-2023 22:48:43] NOTICE: exiting, bye-bye!
2023-06-18 17:48:39 You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
2023-06-18 17:48:39 E.g. https://internal.ip.of.this.server:8080
2023-06-18 17:48:39 
2023-06-18 17:48:39 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:
2023-06-18 17:48:39 https://your-domain-that-points-to-this-server.tld:8443
2023-06-18 17:53:07 Cannot connect to the docker socket. Cannot proceed.
2023-06-18 17:53:10 Cannot connect to the docker socket. Cannot proceed.

Is there anyway to correct this error without starting all the way over. My installation has 151 GB of backed up files that thankfully I can still access. I believe I have a backup as well.

jtr · July 3, 2023, 3:36pm

Might be this:

github.com/nextcloud/all-in-one

docker desktop - connecting to docker socket inside container with different user than root is broken after updating to 4.19

opened 12:07PM - 01 May 23 UTC

szaimen

1. to develop bug documentation help wanted high upstream blocked

This is a Docker Desktop 4.19 bug. See https://github.com/docker/for-win/issues…/13447 and https://github.com/docker/for-mac/issues/6823 Workaround for now: revert back to Docker Desktop 4.18. See https://github.com/docker/for-win/issues/13447#issuecomment-1579399130

AKA:

github.com/docker/for-win

connecting to docker socket inside container with different user than root is broken after updating to 4.19

opened 01:15PM - 01 May 23 UTC

szaimen

status/acknowledged

- [x] I have tried with the latest version of Docker Desktop - [x] I have tried disabling enabled experimental features - [x] I have uploaded Diagnostics - Diagnostics ID: C857ED5F-7E60-421A-ADEE-29B71A07CE6A/20230501125903 ### Actual behavior After updating Docker Desktop on Windows to v4.19 when trying to connect to a bind-mounted tcp unix socket inside a container that runs as unprivileged (non-root user) process. Connecting to the socket as root user inside the container still works but it apparently broke due to the update because it worked also with the unprivileged user before the update. ### Expected behavior It should be possible to connect to the socket even as non-root user if read permissions are set correct. ### Information  - Windows Version: Windows 11 Pro 22H2 - Docker Desktop Version: 4.19 - WSL2 or Hyper-V backend? WSL2 - Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No ### Output of `& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check` ### Steps to reproduce the behavior 1. Update to Docker Desktop 4.19 on Windows 2. run via command prompt: ``` # docker info works with root user docker run -it --rm -v //var/run/docker.sock:/var/run/docker.sock:ro docker:cli docker info ``` <details><summary>Output</summary> ``` Client: Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.10.4 Path: /usr/local/libexec/docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.17.3 Path: /usr/local/libexec/docker/cli-plugins/docker-compose Server: Containers: 2 Running: 2 Paused: 0 Stopped: 0 Images: 4 Server Version: 23.0.5 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Using metacopy: false Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 1 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 runc Default Runtime: runc Init Binary: docker-init containerd version: 2806fc1057397dbaeefbea0e4e17bddfbd388f38 runc version: v1.1.5-0-gf19387a init version: de40ad0 Security Options: seccomp Profile: builtin Kernel Version: 5.15.90.1-microsoft-standard-WSL2 Operating System: Docker Desktop OSType: linux Architecture: x86_64 CPUs: 8 Total Memory: 7.682GiB Name: docker-desktop ID: 98271cca-a380-4fa6-8246-56d88c255a12 Docker Root Dir: /var/lib/docker Debug Mode: false HTTP Proxy: http.docker.internal:3128 HTTPS Proxy: http.docker.internal:3128 No Proxy: hubproxy.docker.internal Registry: https://index.docker.io/v1/ Experimental: true Insecure Registries: hubproxy.docker.internal:5555 127.0.0.0/8 Live Restore Enabled: false WARNING: No blkio throttle.read_bps_device support WARNING: No blkio throttle.write_bps_device support WARNING: No blkio throttle.read_iops_device support WARNING: No blkio throttle.write_iops_device support ``` </details> ``` # docker info does not work with different user even though it has read access to the socket docker run -it --rm -v //var/run/docker.sock:/var/run/docker.sock:ro docker:cli sh -c "apk add shadow sudo && ls -l /var/run/docker.sock && adduser -D -S www-data -G www-data && sudo -u www-data docker info" ``` <details><summary>Output</summary> ``` fetch https://dl-cdn.alpinelinux.org/alpine/v3.17/main/x86_64/APKINDEX.tar.gz fetch https://dl-cdn.alpinelinux.org/alpine/v3.17/community/x86_64/APKINDEX.tar.gz (1/3) Installing linux-pam (1.5.2-r1) (2/3) Installing shadow (4.13-r0) (3/3) Installing sudo (1.9.12_p2-r1) Executing busybox-1.35.0-r29.trigger OK: 17 MiB in 25 packages srwxr-xr-x 1 root root 0 May 1 12:49 /var/run/docker.sock Client: Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.10.4 Path: /usr/local/libexec/docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.17.3 Path: /usr/local/libexec/docker/cli-plugins/docker-compose Server: ERROR: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/info": dial unix /var/run/docker.sock: connect: permission denied errors pretty printing info ``` </details>

Which appears to have been fixed in the release from a couple days ago (just after yours) of DD:

szaimen · July 10, 2023, 9:17am

Indeed the issue should be fixed with Docker Desktop 4.21.1. See connecting to docker socket inside container with different user than root is broken after updating to 4.19 · Issue #13447 · docker/for-win · GitHub

KeithGP · July 11, 2023, 9:36pm

@jtr and @szaimen Thank you. THIS indeed fixed my issue! It broke on 4.19. I updated to 4.20.1 and it was still broken. Today, I updated to 4.21.1 and the bug is fixed. My smartphones are busy backing up as we speak!

THANK YOU!!!