Anonymous volume created for nextcloud-aio-database when using mastercontainer approach with Tailscale (no reverse proxy)

[prashantmall1997]

Environment

• Nextcloud AIO version: v13.0.4
• Installation method: Mastercontainer via Docker Compose (Portainer)
• Setup guide followed: Easy setup: Container-less Tailscale as reverse proxy #6817 (Tailscale, no reverse proxy)
• Host OS: Ubuntu 24.04 on Proxmox VE 8
• Docker version: 29.5.0

Issue

When using the mastercontainer approach, an anonymous volume is created alongside the properly named nextcloud_aio_database volume. The anonymous volume belongs to the nextcloud-aio-database container, verified with:

docker ps -a --filter volume=<hash> --format "{{.Names}}" which returns nextcloud-aio-database

All other volumes are correctly named with the nextcloud_aio_ prefix. Only the database container produces an anonymous volume.

Root cause (from DeepWiki analysis)

The PostgreSQL image defines /mnt/data as a VOLUME instruction in its Dockerfile. In the mastercontainer approach, AIO's orchestration via containers.json maps nextcloud_aio_database_dump to this path — but something in the dynamic container creation is not applying this mapping correctly, causing Docker to fall back to an anonymous volume. This does not affect the manual install (latest.yml) which explicitly declares all named volumes including nextcloud_aio_database_dump.

Expected behavior

No anonymous volumes should be created, consistent with the maintainer's own test server as shown in discussion #6848.

Request

Could the mastercontainer orchestration logic be updated to ensure nextcloud_aio_database_dump is always explicitly mapped, preventing Docker from creating an anonymous volume for the PostgreSQL /mnt/data path?

[szaimen]

Hi, lets track this in #8155