NC AIO in OMV - user permissions wrong

bassguitarist · May 29, 2026, 10:17am

Support intro

Sorry to hear you’re facing problems.

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

Official documentation (searchable and regularly updated)
How to topics and FAQs
Forum search

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can.

The Basics

Nextcloud Server version (e.g., 29.x.x):
- Cannot check, hopefully the latest
Operating system and version (e.g., Ubuntu 24.04):
- OpenMediaVault 8 (based on Debian Trixie)
Web server and version (e.g, Apache 2.4.25):
- Cannot check
Reverse proxy and version _(e.g. nginx 1.27.2)
- Ngnix Proxy Manager 2.1.0
PHP version (e.g, 8.3):
- Cannot check
Is this the first time you’ve seen this error? (Yes / No):
- Yes
When did this problem seem to first start?
- After mastercontainer update from the Administration web interface
Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
- AIO
Are you using CloudfIare, mod_security, or similar? (Yes / No)
- No

Summary of the issue you are facing:

I’m a newbie on NC, while enthusiast user with medium/low competencies in linux management…

I’m not able to anymore start the nextcloud AIO container (and all the others linked to) from the Compose Plugin in my OMV system.

Other containers work without issues.

Steps to replicate it (hint: details matter!):

Nextcloud AIO compose setup in OMV plugin as follows

services:
  nextcloud-aio-mastercontainer:
    image: ghcr.io/nextcloud-releases/all-in-one:latest 
    init: true
    restart: always
    container_name: nextcloud-aio-mastercontainer
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config 
      - /var/run/docker.sock:/var/run/docker.sock:ro 
    network_mode: bridge
    dns:
      - 114.114.114.114
      - 8.8.8.8
    ports:
      - 8000:8080
      - 8043:8443
    environment: 
      APACHE_PORT: 11000

volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer

Have a running installation of NC
Enter the Administrator Web interface
Upgrade to the newest available version (as of 2026, May 26th)
Try restarting the container: it doesn’t work now, see log entries below
Try messing up the system with “chown” and “chmod” and the disaster is served.

Log entries

Nextcloud

nextcloud-aio-mastercontainer  | sudo: unable to execute /usr/bin/test: Permission denied
nextcloud-aio-mastercontainer  | Trying to fix docker.sock permissions internally...
nextcloud-aio-mastercontainer  | Creating docker group internally with id 990
nextcloud-aio-mastercontainer  | sudo: unable to execute /usr/bin/test: Permission denied
nextcloud-aio-mastercontainer  | Docker socket is not readable by the www-data user. Cannot continue.
nextcloud-aio-mastercontainer  | sudo: unable to execute /usr/bin/test: Permission denied
nextcloud-aio-mastercontainer  | Trying to fix docker.sock permissions internally...
nextcloud-aio-mastercontainer  | Adding internal www-data to group docker
nextcloud-aio-mastercontainer  | sudo: unable to execute /usr/bin/test: Permission denied
nextcloud-aio-mastercontainer  | Docker socket is not readable by the www-data user. Cannot continue.
nextcloud-aio-mastercontainer  | sudo: unable to execute /usr/bin/test: Permission denied
nextcloud-aio-mastercontainer  | Trying to fix docker.sock permissions internally...
nextcloud-aio-mastercontainer  | Adding internal www-data to group docker
nextcloud-aio-mastercontainer  | sudo: unable to execute /usr/bin/test: Permission denied
nextcloud-aio-mastercontainer  | Docker socket is not readable by the www-data user. Cannot continue.
nextcloud-aio-mastercontainer  | sudo: unable to execute /usr/bin/test: Permission denied
nextcloud-aio-mastercontainer  | Trying to fix docker.sock permissions internally...
nextcloud-aio-mastercontainer  | Adding internal www-data to group docker
nextcloud-aio-mastercontainer  | sudo: unable to execute /usr/bin/test: Permission denied
nextcloud-aio-mastercontainer  | Docker socket is not readable by the www-data user. Cannot continue.
nextcloud-aio-mastercontainer  | sudo: unable to execute /usr/bin/test: Permission denied
nextcloud-aio-mastercontainer  | Trying to fix docker.sock permissions internally...
nextcloud-aio-mastercontainer  | Adding internal www-data to group docker
nextcloud-aio-mastercontainer  | sudo: unable to execute /usr/bin/test: Permission denied
nextcloud-aio-mastercontainer  | Docker socket is not readable by the www-data user. Cannot continue.
nextcloud-aio-mastercontainer  | sudo: unable to execute /usr/bin/test: Permission denied
nextcloud-aio-mastercontainer  | Trying to fix docker.sock permissions internally...
nextcloud-aio-mastercontainer  | Adding internal www-data to group docker
nextcloud-aio-mastercontainer  | sudo: unable to execute /usr/bin/test: Permission denied
nextcloud-aio-mastercontainer  | Trying to fix docker.sock permissions internally...
nextcloud-aio-mastercontainer  | Adding internal www-data to group docker
nextcloud-aio-mastercontainer  | sudo: unable to execute /usr/bin/test: Permission denied
nextcloud-aio-mastercontainer  | sudo: unable to execute /usr/bin/test: Permission denied
nextcloud-aio-mastercontainer  | Docker socket is not readable by the www-data user. Cannot continue.
nextcloud-aio-mastercontainer  | Docker socket is not readable by the www-data user. Cannot continue.

nextcloud-aio-mastercontainer exited with code 1 (restarting)
nextcloud-aio-mastercontainer  | sudo: unable to execute /usr/bin/test: Permission denied
nextcloud-aio-mastercontainer  | Trying to fix docker.sock permissions internally...
nextcloud-aio-mastercontainer  | Adding internal www-data to group docker
nextcloud-aio-mastercontainer  | sudo: unable to execute /usr/bin/test: Permission denied
nextcloud-aio-mastercontainer  | Docker socket is not readable by the www-data user. Cannot continue.

Web Browser

Not accessible

PASTE

Web server / Reverse Proxy

I’m running Ngnix in another system (home assistant plugin, that is the machine connected to internet).By the way, I guess that Ngnix is not yet part of the problem since NC AIO container does not run.

Configuration

Nextcloud

Not sure where to check for.

PASTE HERE

Kerasit · May 29, 2026, 11:42am

All the missing info for the support ticket where you wrote you do not know, is available here:

https://yourdomain.dom/settings/admin/serverinfo → Replace yourdomain.dom with your actual website url of you nextcloud installation.

https://yourdomain.dom/settings/admin/overview → here you can see version of NC

bassguitarist · May 29, 2026, 1:21pm

Thanks for your kind answer.

By the way, as written, i cannot start the container, so the website is not accessible.

bassguitarist · June 1, 2026, 8:07am

I ended with saving the “volumes” of my docker folder tree, deleting everything else and restarting from scratch.

Luckily I setup borg backup, who did the magic to restore everything as it was before my mess.

Thanks indeed for your attention.