feat(compose): show docker-compose named volumes as read-only in Advanced → Volumes

[tobeefornottobeef]

What problem will this feature address?

For Docker Compose apps, Dokploy supports named volumes in docker-compose.yml, but the Advanced → Volumes screen shows No volumes/mounts configured and Add Volume opens a modal with only File Mount available.

That makes it look like the app has no persistent storage configured even when runtime mounts exist and Dokploy is actively using them. In practice, this makes the UI hard to trust as an operational source of truth for Compose services.

I understand from issue #866 and closed PR #3344 that the maintainers do not want a second UI path that edits Compose volumes directly, because the YAML should remain the declarative source of truth. I agree with that constraint.

The missing piece is read-only visibility: operators still need a simple place in Dokploy to confirm which named volumes are attached to a Compose app without having to jump to the raw YAML, container inspect output, or backup flows.

Describe the solution you'd like

Please show Docker Compose named volumes in Advanced → Volumes as a read-only inventory, sourced from the compose file and/or resolved runtime mounts.

Important constraints:

• Keep docker-compose.yml as the only editable source of truth
• Do not add create/update/delete controls for Compose named volumes in that screen
• Clearly label these rows as something like Compose-defined or Read only
• If useful, also display the resolved Docker volume name (for example {appName}_{volumeName}) and mount path

This would preserve the declarative Compose model while making the Dokploy UI trustworthy for day-2 operations.

Describe alternatives you've considered

Current workarounds are:

1. Open the raw docker-compose.yml and inspect the volumes: section manually
2. Check Containers → View Mounts to inspect live runtime mounts
3. Use Volume Backups flows, which can also discover Compose volumes indirectly
4. SSH into the server and run docker inspect / docker volume ls

Those work, but they scatter the information across multiple places and make the main Volumes screen misleading for Compose apps. A read-only inventory in the existing screen would solve that without violating the maintainers' declarative-model concerns from PR #3344.

Additional context

Observed on Dokploy v0.29.8.

Repro:

1. Deploy a Docker Compose app with named volumes, e.g.

   services:
     app:
       volumes:
         - app-data:/data
   volumes:
     app-data:

2. Confirm the container really has the volume mounted via docker inspect
3. Open Advanced → Volumes in Dokploy
4. Notice it says No volumes/mounts configured
5. Click Add Volume and notice only File Mount is available

This request is intentionally not asking for YAML editing through the Volumes UI — only for visibility.

Will you send a PR to implement it?

Maybe, need help

[zexxitywave]

I'd like to investigate and work on this issue.

From an initial review, it looks like Compose-defined volumes are already parsed from the compose specification, but the Advanced → Volumes view currently renders only mount records returned by the backend. I'll explore exposing Compose-defined volumes as read-only entries while keeping docker-compose.yml as the sole source of truth, then submit a PR if the approach aligns with the intended design.