[BUG] Docker compose down doesnt' remove orphan volumes.

[wclr]

Description

I'm not sure if there is a reason or if it is just an oversight.

But docker compose down --remove-orphans -v doesn't remove orphan volumes of the project, have to clean up manually with docker volume rm.

Steps To Reproduce

No response

Compose Version

Docker Compose version v2.40.3-desktop.1

Docker Environment

Client:
 Version:           28.5.1
 API version:       1.51
 Go version:        go1.24.8
 Git commit:        e180ab8
 Built:             Wed Oct  8 12:19:16 2025
 OS/Arch:           windows/amd64
 Context:           desktop-linux

Server: Docker Desktop 4.49.0 (208700)
 Engine:
  Version:          28.5.1
  API version:      1.51 (minimum version 1.24)
  Go version:       go1.24.8
  Git commit:       f8215cc
  Built:            Wed Oct  8 12:17:24 2025
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.27
  GitCommit:        05044ec0a9a75232cad458027ca83437aae3f4da
 runc:
  Version:          1.2.5
  GitCommit:        v1.2.5-0-g59923ef
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Anything else?

No response

[ndeloof]

I can't reproduce:

$  cat compose.yaml 
services:
  app:
    image: nginx
    volumes:
      - /tmp

$ docker volume ls
DRIVER    VOLUME NAME

$ docker compose up -d
[+] up 1/1
 ✔ Container truc-app-1 Created                                                                                    0.1s 

$ docker volume ls
DRIVER    VOLUME NAME
local     3aefde1dd451035dbebcbfc76d9b095b0da902361333cc95e58bce0c63f7af5d

$ docker compose down -v
[+] down 2/2
 ✔ Container truc-app-1 Removed                                                                                    0.2s 
 ✔ Network truc_default Removed                                                                                    0.2s 

$ docker volume ls
DRIVER    VOLUME NAME

Maybe there's misunderstanding about "orphan volumes" here?

[wclr]

By orphan volumes I mean volumes that belonged no to existing service (belonged to a prior removed service), so they exit without service). Also it would be good if such volumes would be removed on docker compose up --remove-orphans or some by other special flag. Just to keep things clean, because eventually there may be a pile of such derelict guys
.

[ndeloof]

oh ok, so such a volume doesn't exists in the compose.yaml and you expect compose to "garbage collect".
Such feature doesn't exists indeed, to be considered ...

[wclr]

Yes, this is not a bug probably, but not considered though expected feature.