[Help] Nextcloud AIO from TOS 5.1.145 to TOS 6.0
Posted: 06 Jan 2026, 01:14
Hello,
I have recently updated my NAS from TOS 5.1.145 to TOS 6.0. I then reinstalled docker engine and tried to restart my Nextcloud server which was running via a docker container with Nextcloud All-In-One (https://github.com/nextcloud/all-in-one).
However i encountered this error when running it :
On my NAS, I indeed have :
It seams Nextcloud AIO does not like the switch to user "being root" (UID 0) and root being UID 9999 on TOS 6.0
Do you have an idea on how to fix this issue ?
I have recently updated my NAS from TOS 5.1.145 to TOS 6.0. I then reinstalled docker engine and tried to restart my Nextcloud server which was running via a docker container with Nextcloud All-In-One (https://github.com/nextcloud/all-in-one).
However i encountered this error when running it :
Code: Select all
> sudo docker run \
--init \
--sig-proxy=false \
--name nextcloud-aio-mastercontainer \
--restart always \
--publish 80:80 \
--publish 8080:8080 \
--publish 8443:8443 \
--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \
--volume /var/run/docker.sock:/var/run/docker.sock:ro \
ghcr.io/nextcloud-releases/all-in-one:latest
sudo: /etc/sudo.conf is owned by uid 9999, should be 0
sudo: /etc/sudo.conf is owned by uid 9999, should be 0
sudo: /etc/sudoers is owned by uid 9999, should be 0
sudo: error initializing audit plugin sudoers_audit
Trying to fix docker.sock permissions internally...
Creating docker group internally with id 1000
sudo: /etc/sudo.conf is owned by uid 9999, should be 0
sudo: /etc/sudo.conf is owned by uid 9999, should be 0
sudo: /etc/sudoers is owned by uid 9999, should be 0
sudo: error initializing audit plugin sudoers_audit
Docker socket is not readable by the www-data user. Cannot continue.Code: Select all
MyUsername:x:0:0:TOS User
root:x:9999:9999:Linux UserDo you have an idea on how to fix this issue ?