From df185b501abcf89a33e93243301514aece073708 Mon Sep 17 00:00:00 2001
From: Allie Sadler <102604716+aevesdocker@users.noreply.github.com>
Date: Thu, 9 Oct 2025 10:28:44 +0100
Subject: [PATCH] Compose volume clarity (#23531)

<!--Delete sections as needed -->

## Description

addresses
https://docker.slack.com/archives/C04BMTUC41E/p1759908356837639

## Related issues or tickets

<!-- Related issues, pull requests, or Jira tickets -->

## Reviews

<!-- Notes for reviewers here -->
<!-- List applicable reviews (optionally @tag reviewers) -->

- [ ] Technical review
- [ ] Editorial review
- [ ] Product review
---
 content/reference/compose-file/volumes.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/content/reference/compose-file/volumes.md b/content/reference/compose-file/volumes.md
index 64e826f580..04c1b5ae96 100644
--- a/content/reference/compose-file/volumes.md
+++ b/content/reference/compose-file/volumes.md
@@ -120,6 +120,10 @@ volumes:
 
 Compose sets `com.docker.compose.project` and `com.docker.compose.volume` labels.
 
+> [!NOTE]
+>
+> Labels defined here apply to named volumes only. They’re stored on the volume resource and visible via `docker volume inspect`. They do not apply to bind mounts and do not change mount semantics.
+
 ### `name`
 
 `name` sets a custom name for a volume. The name field can be used to reference volumes that contain special