# rootless Docker Nextcloud AIO

**URL:** <https://help.nextcloud.com/t/rootless-docker-nextcloud-aio/240547>\
**Category:** ℹ️ Support\
**Tags:** nc32, external\_storage, smb, aio\
**Created:** [February 18, 2026, 1:54pm UTC](https://help.nextcloud.com/t/rootless-docker-nextcloud-aio/240547 "2026-02-18T13:54:31Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![edapx](https://help.nextcloud.com/letter_avatar/edapx/32/6_22734026db12803ebb3e059622ac3534.png) [@edapx](https://help.nextcloud.com/u/edapx)\
**Post date:** [February 18, 2026, 1:54pm UTC](https://help.nextcloud.com/t/rootless-docker-nextcloud-aio/240547/1 "2026-02-18T13:54:31Z")

</div>

> **Support intro**
>
> ## Sorry to hear you’re facing problems. 🙁
> 
> _The community help forum ([help.nextcloud.com](http://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](http://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](https://docs.nextcloud.com) (searchable and regularly updated)
> - [How to topics and FAQs](https://help.nextcloud.com/c/how-to-faqs/9)
> - [Forum search](https://help.nextcloud.com/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).

## The Basics

- Nextcloud Server version _(e.g., 29.x.x)_:
  - Nextcloud 32.0.5

- Operating system and version _(e.g., Ubuntu 24.04)_:
  - `Ubuntu 24.04`

- Is this the first time you’ve seen this error? (Yes / No):
  - `Yes`

- When did this problem seem to first start?
  - `Since installation`

- 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 am having problems installing Nextcloud AIO with docker rootless. Specifically, I have a problems with file permission. This is the situation of my containers:

 ![image](https://help.nextcloud.com/uploads/default/original/3X/f/4/f468c331fd085c03711b10f57492b0520a4af197.png)

Apache and Notify Push can’t ping Nextcloud. So I hope that when the Nextcloud work the other two will start to work as well. Yesterday the nextcloud container was not working because of this error:

```auto

Connection to nextcloud-aio-database (172.18.0.7) 5432 port [tcp/postgresql] succeeded!

+ '[' -f /dev-dri-group-was-added ']'

++ find /dev -maxdepth 1 -mindepth 1 -name dri

+ '[' -n '' ']'

+ set +x

chown: cannot read directory '/mnt/ncdata': Permission denied

chmod: changing permissions of '/mnt/ncdata': Operation not permitted

chmod: cannot read directory '/mnt/ncdata': Permission denied

rm: cannot remove '/mnt/ncdata/this-is-a-test-file': Permission denied

Connection to nextcloud-aio-redis (172.18.0.9) 6379 port [tcp/redis] succeeded!

touch: cannot touch '/mnt/ncdata/this-is-a-test-file': Permission denied

The www-data user does not appear to have access rights to the data directory.

It is possible that the files are on a filesystem that does not support standard Linux permissions,

or the permissions simply need to be adjusted. Please change the permissions as described below.

Current permissions are:

65534:65534 750

(userID:groupID permissions)

They should be:

33:0 750

(userID:groupID permissions)

Also, ensure that all parent directories on the host of your chosen data directory are publicly readable.

For example: sudo chmod +r /mnt (adjust this command as needed).

If you want to use a FUSE mount as the data directory, add 'allow_other' as an additional mount option.

For SMB/CIFS mounts as the data directory, see:

  https://github.com/nextcloud/all-in-one#can-i-use-a-cifssmb-share-as-nextclouds-datadir

Connection to nextcloud-aio-database (172.18.0.7) 5432 port [tcp/postgresql] succeeded!

+ '[' -f /dev-dri-group-was-added ']'

++ find /dev -maxdepth 1 -mindepth 1 -name dri

+ '[' -n '' ']'

+ set +x

chown: cannot read directory '/mnt/ncdata': Permission denied

chmod: changing permissions of '/mnt/ncdata': Operation not permitted

chmod: cannot read directory '/mnt/ncdata': Permission denied

rm: cannot remove '/mnt/ncdata/this-is-a-test-file': Permission denied

Connection to nextcloud-aio-redis (172.18.0.9) 6379 port [tcp/redis] succeeded!

touch: cannot touch '/mnt/ncdata/this-is-a-test-file': Permission denied

The www-data user does not appear to have access rights to the data directory.

It is possible that the files are on a filesystem that does not support standard Linux permissions,

or the permissions simply need to be adjusted. Please change the permissions as described below.

Current permissions are:

65534:65534 750

(userID:groupID permissions)

They should be:

33:0 750

(userID:groupID permissions)

```

I have read then about “Rootless Mapping Math“, and the fact that the folder `NEXTCLOUD_DATADIR` should belong to ``100032:100032`` [all-in-one/docker-rootless.md at main · nextcloud/all-in-one · GitHub](https://github.com/nextcloud/all-in-one/blob/main/docker-rootless.md#note-regarding-permissions) .Changing the permission to that folder fixed the permission error, But now `docker logs nextcloud-aio-nextcloud --tail 50` returns another error.

```auto
2026-02-18 14:21:23.51648+01
(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.7) 6379 port [tcp/redis] succeeded!
The initial Nextcloud installation failed.
For more information about what went wrong, check the logs above.
Please reset AIO properly and try again.
See:

Connection to nextcloud-aio-database (172.18.0.10) 5432 port [tcp/postgresql] succeeded!
now

2026-02-18 14:22:26.240897+01
(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.7) 6379 port [tcp/redis] succeeded!
The initial Nextcloud installation failed.
For more information about what went wrong, check the logs above.
Please reset AIO properly and try again.
See: https://github.com/nextcloud/all-in-one#how-to-properly-reset-the-instance

Connection to nextcloud-aio-database (172.18.0.10) 5432 port [tcp/postgresql] succeeded!
now

2026-02-18 14:23:28.98202+01
(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.7) 6379 port [tcp/redis] succeeded!
The initial Nextcloud installation failed.
For more information about what went wrong, check the logs above.
Please reset AIO properly and try again.
See:
https://github.com/nextcloud/all-in-one#how-to-properly-reset-the-instance

```

My question is, what to do now? Am I supposed to change the permission of the volumes too? They are currently 1000:1000

`me@host:/data/docker/volumes$ ls -nd *`  
`brw------- 1 1000 1000 252, 0 Feb 15 14:04 backingFsBlockDev`  
`-rw------- 1 1000 1000 32768 Feb 18 13:05 metadata.db`  
`drwx-----x 3 1000 1000 4096 Feb 16 22:43 nextcloud_aio_apache`  
`drwx-----x 3 1000 1000 4096 Feb 16 22:42 nextcloud_aio_database`  
`drwx-----x 3 1000 1000 4096 Feb 16 22:42 nextcloud_aio_database_dump`  
`drwx-----x 3 1000 1000 4096 Feb 16 22:36 nextcloud_aio_mastercontainer`  
`drwx-----x 3 1000 1000 4096 Feb 16 22:42 nextcloud_aio_nextcloud`  
`drwx-----x 3 1000 1000 4096 Feb 16 22:42 nextcloud_aio_redis`

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

1. Try to install nextcloud AIO as docker rootless following the instructions [all-in-one/docker-rootless.md at main · nextcloud/all-in-one · GitHub](https://github.com/nextcloud/all-in-one/blob/main/docker-rootless.md#note-regarding-permissions)

### 

###

---

<div class="post-metadata">

**Author:** ![szaimen](https://help.nextcloud.com/user_avatar/help.nextcloud.com/szaimen/32/63019_2.png) [@szaimen](https://help.nextcloud.com/u/szaimen)\
**Post date:** [February 18, 2026, 1:55pm UTC](https://help.nextcloud.com/t/rootless-docker-nextcloud-aio/240547/2 "2026-02-18T13:55:03Z")

</div>

Hi, please check [all-in-one/docker-rootless.md at main · nextcloud/all-in-one · GitHub](https://github.com/nextcloud/all-in-one/blob/main/docker-rootless.md)

---

<div class="post-metadata">

**Author:** ![edapx](https://help.nextcloud.com/letter_avatar/edapx/32/6_22734026db12803ebb3e059622ac3534.png) [@edapx](https://help.nextcloud.com/u/edapx)\
**Post date:** [February 18, 2026, 2:06pm UTC](https://help.nextcloud.com/t/rootless-docker-nextcloud-aio/240547/3 "2026-02-18T14:06:21Z")

</div>

Well, that link is the document where I have start from. Which part of the doc you do not see reflected in my post?

---

<div class="post-metadata">

**Author:** ![szaimen](https://help.nextcloud.com/user_avatar/help.nextcloud.com/szaimen/32/63019_2.png) [@szaimen](https://help.nextcloud.com/u/szaimen)\
**Post date:** [February 18, 2026, 2:09pm UTC](https://help.nextcloud.com/t/rootless-docker-nextcloud-aio/240547/4 "2026-02-18T14:09:20Z")

</div>

Probably this one: [all-in-one/docker-rootless.md at c5b088ef3385fb5119f1551b225b275132972b92 · nextcloud/all-in-one · GitHub](https://github.com/nextcloud/all-in-one/blob/c5b088ef3385fb5119f1551b225b275132972b92/docker-rootless.md?plain=1#L20-L21)

---

<div class="post-metadata">

**Author:** ![edapx](https://help.nextcloud.com/letter_avatar/edapx/32/6_22734026db12803ebb3e059622ac3534.png) [@edapx](https://help.nextcloud.com/u/edapx)\
**Post date:** [February 18, 2026, 2:13pm UTC](https://help.nextcloud.com/t/rootless-docker-nextcloud-aio/240547/5 "2026-02-18T14:13:58Z")

</div>

I can confirm that all the volumes belong to the user running docker rootless

---

<div class="post-metadata">

**Author:** ![szaimen](https://help.nextcloud.com/user_avatar/help.nextcloud.com/szaimen/32/63019_2.png) [@szaimen](https://help.nextcloud.com/u/szaimen)\
**Post date:** [February 18, 2026, 2:33pm UTC](https://help.nextcloud.com/t/rootless-docker-nextcloud-aio/240547/6 "2026-02-18T14:33:31Z")

</div>

Did you see the note about the userid and groupid `100032:100032` ?

---

<div class="post-metadata">

**Author:** ![szaimen](https://help.nextcloud.com/user_avatar/help.nextcloud.com/szaimen/32/63019_2.png) [@szaimen](https://help.nextcloud.com/u/szaimen)\
**Post date:** [February 18, 2026, 2:34pm UTC](https://help.nextcloud.com/t/rootless-docker-nextcloud-aio/240547/7 "2026-02-18T14:34:38Z")

</div>

Btw, this is probably easier to read: [all-in-one/docker-rootless.md at main · nextcloud/all-in-one · GitHub](https://github.com/nextcloud/all-in-one/blob/main/docker-rootless.md#note-regarding-permissions)

---

<div class="post-metadata">

**Author:** ![edapx](https://help.nextcloud.com/letter_avatar/edapx/32/6_22734026db12803ebb3e059622ac3534.png) [@edapx](https://help.nextcloud.com/u/edapx)\
**Post date:** [February 18, 2026, 3:02pm UTC](https://help.nextcloud.com/t/rootless-docker-nextcloud-aio/240547/8 "2026-02-18T15:02:29Z")

</div>

> [@edapx](#):
>
> `https://github.com/nextcloud/all-in-one#how-to-properly-reset-the-instance`

yes, this is the tutorial that I was following.  
I have removed /data/nextcloud, and created a new folder with a different name, but same permission. I have set the path of that folder for the variable NEXTCLOUD\_DATADIR in the compose.yml file.  
The permission to the backup and nextcloud folder have been set with sudo chown -R 100032:100032.

I have just reset the instances following this [GitHub - nextcloud/all-in-one: 📦 The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.](https://github.com/nextcloud/all-in-one#how-to-properly-reset-the-instance)

Then recreated again the containers with compose up -d.

And it finally worked. What I think was happening is that the content of the nextcloud folder from the previous docker root installation was interferring with the creation process.

---

<div class="post-metadata">

**Author:** ![edapx](https://help.nextcloud.com/letter_avatar/edapx/32/6_22734026db12803ebb3e059622ac3534.png) [@edapx](https://help.nextcloud.com/u/edapx)\
**Post date:** [February 18, 2026, 3:03pm UTC](https://help.nextcloud.com/t/rootless-docker-nextcloud-aio/240547/9 "2026-02-18T15:03:19Z")

</div>

Yes, it is in my first post, thanks

---

<div class="post-metadata">

**Author:** ![system](https://help.nextcloud.com/user_avatar/help.nextcloud.com/system/32/29333_2.png) [@system](https://help.nextcloud.com/u/system)\
**Post date:** [February 26, 2026, 3:03pm UTC](https://help.nextcloud.com/t/rootless-docker-nextcloud-aio/240547/10 "2026-02-26T15:03:54Z")

</div>

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.