Now I just saw that version 12 is out of beta and thought, cool — let’s upgrade.
So I went into my admin area and tried to open the AIO interface. But every time, I get: “Connection refused.”
I restarted my Pi and tried everything else — nothing. When I went into Portainer to restart the master container, I noticed IT’S GONE.
I tried all kinds of Docker commands, nothing.
I thought, well, I’ll just stop all the other containers and run Docker Compose again, that way I’ll get the latest version and it will update the containers.
Yeah, sure… now I get:
Trying to fix docker.sock permissions internally…
Adding internal www-data to group ntp
Cannot connect to the docker socket. Cannot proceed.
Did you maybe remove group read permissions for the docker socket? AIO needs them in order to access the docker socket.
I am having the same issue after last nights automatic upgrade. Getting the same docker permission error. I am running on Synology NAS with latest DSM 7.2.2
After downgrading MasterContainer with nextcloud/all-in-one:20250325_084656 everything starts as it should.
I tried to add the ‘–security-opt label=disable’ for troubleshooting but no luck before downgrading.
As the docker packages from the debian// raspian repository are always behind the official relase, I upgraded the docker installation with the docker installation script.
This upgraded the docker version to v29 and after a reboot the mastercontainer starts up again - without the need to downgrade the docker-api version.
After this the nextcloud-aio could be upgraded to the hub25 autumn release.
My AIO on Synology is also crashed now and the AIO admin UI is not accessible.
Now I learned that my Synology docker is too old - however it the latest offered by Synology currently.
~$ sudo docker version
Client:
Version: 20.10.3
API version: 1.41
Go version: go1.17.1
Git commit: 55f0773
Built: Thu Jul 21 10:23:46 2022
OS/Arch: linux/amd64
Context: default
Experimental: true
I understand that this version is pretty old but I wonder where I have overseen the warning that it will crash my Nextlcloud with the update - where could I have seen it coming?
Is there a guide how to rollback the instance with my just created backup - without the UI?
There is a guide : #how-to-properly-reset-the-instance but this is NOT for instances with existing data.
Thanks for your help!
I had checked that before, and I think their were no helpful procedure for me . My docker and docker API and the DSM 7.1 are too old. Updating Docker alone was risky (> other containers) , as was a sudden, poorly prepared update of the entire DSM from version 1.7.1 to 1.7.2.
Possibly, I did not fully understand the hints from ‘ralfboernemeier’ to ‘mikkebakke’
My solution was this: I had a RaspberryPi 5 with trixi and USB-SSD, intended to be a test site for the AIO borg backup. It became my productive environment now. The backup restore test was successful .
What I did not find but expected was a described roll-back procedure. Simply to find the time for a proper update phase. Maybe a sample compose.yaml with the right version tags. That would be a safeguard for the future.
Great to see that there is a “refactor docker api version check #7234”
)
.