Support intro
I am using the AIO docker version of NC ( Nextcloud AIO v9.7.0)
Yesterday, accessing the control panel I saw that there was an update and I performed the usual procedure:
from the management page I stopped the containers and then I started the update which however did not complete correctly.
Three containers (certainly apache, push and another that I do not remember) did not restart and warned me that they were in a loop and to try to shut down and restart the containers… but nothing to do, it did not work.
I entered the apache container to see the logs but I did not find anything interesting.
What can I do? In which log should I look?
root@raspi4misc:~# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e4b0a25330e5 nextcloud/aio-apache:latest-arm64 "/start.sh /usr/bin/…" 10 hours ago Up 10 hours (healthy) 80/tcp, 0.0.0.0:11000->11000/tcp, :::11000->11000/tcp nextcloud-aio-apache
5f1dc364162f nextcloud/aio-notify-push:latest-arm64 "/start.sh" 10 hours ago Up 10 hours (healthy) nextcloud-aio-notify-push
8ae21061715a nextcloud/aio-nextcloud:latest-arm64 "/start.sh /usr/bin/…" 10 hours ago Restarting (1) 58 seconds ago nextcloud-aio-nextcloud
20c29849ed1f nextcloud/aio-imaginary:latest-arm64 "/start.sh" 10 hours ago Up 10 hours (healthy) nextcloud-aio-imaginary
990ae6aba89a nextcloud/aio-redis:latest-arm64 "/start.sh" 10 hours ago Up 10 hours (healthy) 6379/tcp nextcloud-aio-redis
4c59fdc76221 nextcloud/aio-postgresql:latest-arm64 "/start.sh" 10 hours ago Up 10 hours (healthy) 5432/tcp nextcloud-aio-database
a269fea3fa7a nextcloud/all-in-one:latest-arm64 "/start.sh" 12 hours ago Up 11 hours (healthy) 0.0.0.0:8080->8080/tcp, :::8080->8080/tcp, 0.0.0.0:8443->8443/tcp, :::8443->8443/tcp, 9000/tcp, 0.0.0.0:81->80/tcp, [::]:81->80/tcp nextcloud-aio-mastercontainer
root@raspi4misc:~#
Connection to nextcloud-aio-database (172.18.0.2) 5432 port [tcp/postgresql] succeeded!
now
-------------------------------
2024-10-22 10:02:46.973888+02
(1 row)
+ '[' -f /dev-dri-group-was-added ']'
++ find /dev -maxdepth 1 -mindepth 1 -name dri
+ '[' -n '' ']'
+ set +x
Connection to nextcloud-aio-redis (172.18.0.3) 6379 port [tcp/redis] succeeded!
The last Nextcloud update failed.
Please restore from backup and try again!
If you do not have a backup in place, you can simply delete the update.failed file in the datadir which will allow the container to start again.
Client: Docker Engine - Community
Version: 27.3.1
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.17.1
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.29.7
Path: /usr/libexec/docker/cli-plugins/docker-compose
Server:
Containers: 8
Running: 6
Paused: 0
Stopped: 2
Images: 11
Server Version: 27.3.1
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: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: runc io.containerd.runc.v2
Default Runtime: runc
Init Binary: docker-init
containerd version: 7f7fdf5fed64eb6a7caf99b3e12efcf9d60e311c
runc version: v1.1.14-0-g2c9f560
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 5.15.0-1064-raspi
Operating System: Ubuntu 22.04.5 LTS
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 3.701GiB
Name: raspi4misc
ID: EQIF:MFZH:C66E:24JW:DCUM:VJO4:35YL:FP6G:FZLG:UYYS:V6MQ:ZAQD
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
root@raspi4misc:~#