Feature request: Allow explicit names for AIO Docker volumes to avoid anonymous volumes

[Mitch187]

Hello AIO team, thanks for the great project; could you please provide a way to enforce explicit names for all Docker volumes used by AIO so we don’t end up with anonymous volumes with random IDs .
Anonymous volumes are auto‑generated and persist unless removed with --rm, which makes tracking, backup, and migration harder compared to deterministically named volumes .
Attached is a 3‑level directory listing (created with the tree command or a small script) to illustrate the current structure that would benefit from stable naming across services.

Version: Nextcloud AIO v11.7.0

Request:
Please support deterministic naming for all volumes (for example via Docker Compose’s named volumes with an explicit name: field, or an equivalent mechanism in AIO) so they don’t fall back to anonymous volumes .
Deterministic names simplify scripted backups, cross‑host migrations, and operational troubleshooting, since volumes can be referenced predictably across environments.

Context:
In Docker, a volume may be named or anonymous; anonymous volumes get a unique random name and aren’t automatically reused across containers, which is why consistent naming is desirable in production setups .
The attached 3‑level tree output shows the paths we intend to keep stable, and having named volumes for each of these mount points would make the setup reproducible and easier to maintain .
Thank you for considering this request and for any guidance on the officially supported way to enforce named volumes across all AIO services.

/var/lib/docker/volumes
├── 1a6b355119e2bd12c42ec1c3ff791f214728c2dbd75faaccc110e6c3561e377d
│   └── _data
│   └── mnesia
├── 1c6f21e5f15e0215ddbe929422cfe31035ace21d7337d139a7187cede592ff37
│   └── _data
│   └── 16
├── 23ccf5a0fc14c9972de45a44a0325730c697fdd58d62bd7abfb967e5f44ffda2
│   └── _data
│   ├── documentserver
│   └── documentserver-example
├── 4fd87dc0dd0e9534a547ca77267ec2c17aa209c07e5f0980c2d331d84e6d850b
│   └── _data
├── 8cb3cb487629714b4289d56a9bd0f5399adf1513822161a472b258aed086f6b4
│   └── _data
├── 979d64e45aaf081bcde9e488366fc67a9dfefb394f2f5e645a7e32addcef13b0
│   └── _data
├── nextcloud_aio_apache
│   └── _data
│   └── caddy
├── nextcloud_aio_clamav
│   └── _data
├── nextcloud_aio_database
│   └── _data
│   ├── base
│   ├── global
│   ├── pg_commit_ts
│   ├── pg_dynshmem
│   ├── pg_logical
│   ├── pg_multixact
│   ├── pg_notify
│   ├── pg_replslot
│   ├── pg_serial
│   ├── pg_snapshots
│   ├── pg_stat
│   ├── pg_stat_tmp
│   ├── pg_subtrans
│   ├── pg_tblspc
│   ├── pg_twophase
│   ├── pg_wal
│   └── pg_xact
├── nextcloud_aio_database_dump
│   └── _data
├── nextcloud_aio_elasticsearch
│   └── _data
│   ├── indices
│   ├── snapshot_cache
│   └── _state
├── nextcloud_aio_mastercontainer
│   └── _data
│   ├── caddy
│   ├── certs
│   ├── data
│   └── session
├── nextcloud_aio_nextcloud
│   └── _data
│   ├── 3rdparty
│   ├── apps
│   ├── config
│   ├── core
│   ├── custom_apps
│   ├── data
│   ├── dist
│   ├── lib
│   ├── LICENSES
│   ├── ocs
│   ├── ocs-provider
│   ├── resources
│   ├── themes
│   └── updater
├── nextcloud_aio_nextcloud_data
│   └── _data
│   ├── admin
│   └── appdata_oc*
├── nextcloud_aio_onlyoffice
│   └── _data
│   ├── documentserver
│   └── documentserver-example
├── nextcloud_aio_redis
│   └── _data

Here is my stack:
`services:
nextcloud-aio-mastercontainer:
image: nextcloud/all-in-one:latest
init: true
container_name: nextcloud-aio-mastercontainer # This line is not allowed to be changed as otherwise AIO will not work correctly
hostname: nextcloud-aio-mastercontainer
environment: # Is needed when using any of the options below
APACHE_PORT: 11000
SKIP_DOMAIN_VALIDATION: false
NEXTCLOUD_TRUSTED_DOMAINS: nc.meinedomain.de 192.168.x.x
TRUSTED_PROXIES: 193.x.x.x
NEXTCLOUD_MOUNT: /var/lib/docker/volumes
volumes:
- nextcloud_aio_mastercontainer:/mnt/docker-aio-config # This line is not allowed to be changed as otherwise the built-in backup solution will not work
- /var/run/docker.sock:/var/run/docker.sock:ro # May be changed on macOS, Windows or docker rootless. See the applicable documentation. If adjusting, don't forget to also set 'WATCHTOWER_DOCKER_SOCKET_PATH'!
ports:
- 192.168.x.x:8188:8080
restart: always

volumes: # If you want to store the data on a different drive, see https://github.com/nextcloud/all-in-one#how-to-store-the-filesinstallation-on-a-separate-drive
nextcloud_aio_mastercontainer:
name: nextcloud_aio_mastercontainer # This line is not allowed to be changed as otherwise the built-in backup solution will not work`

Best Regards,
Mitch

[szaimen]

Hi, before we go further into deetails, can you please figure out to which containers the anonymous volumes belong?
For example on my test server, there are none. See

tree -dL 2 /var/lib/docker/volumes/
/var/lib/docker/volumes/
├── nextcloud_aio_apache
│   └── _data
├── nextcloud_aio_backup_cache
│   └── _data
├── nextcloud_aio_clamav
│   └── _data
├── nextcloud_aio_database
│   └── _data
├── nextcloud_aio_database_dump
│   └── _data
├── nextcloud_aio_elasticsearch
│   └── _data
├── nextcloud_aio_jellyfin
│   └── _data
├── nextcloud_aio_jellyseerr
│   └── _data
├── nextcloud_aio_mastercontainer
│   └── _data
├── nextcloud_aio_nextcloud
│   └── _data
├── nextcloud_aio_nextcloud_data
│   └── _data
├── nextcloud_aio_redis
│   └── _data
├── nextcloud_aio_talk_recording
│   └── _data
└── nextcloud_aio_vaultwarden_logs
    └── _data

[Mitch187]

Hi,

thank you for your answer. These are nexcloud volumes i have checked.

Perhaps I should briefly describe what might have led to this, as I now believe this to be the cause.

I have a nextcloud-aio installation on an AMD64 server. I would like to replace this with an ARM64 server, as it offers much better performance and is more affordable (more cores, etc.).

I have now run the identical stack on the ARM64 server (a new_install) via Portainer.

And now these unnamed volumes suddenly appear before I import the data backup from AMD64.

Does anyone have any idea what is going wrong here or how I can find out the names of the unnamed volumes?

Best regards,
Mitch