Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[BUG] down -v removes a named volume owned by another project

Aperta
  • Qualcosa non va?
#14,373 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@htoyoda18 ci sta già lavorando.

Dal 21/10/2026.

  • #14374 di @htoyoda18 — aperta

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
73/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
docker-compose, go
Ambito
devops, tooling

Direzione di ricerca

Start at the down -v volume removal path and compare its ownership handling with the warning emitted by up for a volume labeled with another project name. The issue gives a two project reproduction using the same explicit volume name; run those steps and confirm down -v preserves the other project's volume and warns. No source file or test path is named in the issue.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

kind/bug
Description

When two projects declare a volume with the same explicit name: (without external: true), docker compose down -v in one project removes the volume that the other project created, along with its data.

up already detects this case. It warns volume "..." already exists but was created for project "proja" (expected "projb") and reuses the volume without touching it. down -v makes no such check: it removes the volume by name, with no warning.

A common way to hit this: the same repository checked out in several directories or git worktrees. Each checkout gets its own project name (from its directory), but a volume name: hard-coded in compose.yaml is the same in all of them.

Current behavior: down -v in projb removes proja's volume (Volume n2-shared-data Removed, exit 0).
Expected behavior: down -v only removes volumes this project owns. For a volume labeled for another project, it skips the volume and warns, just as up warns about it.

Steps To Reproduce
  1. Create two directories, proja/ and projb/, each with this compose.yaml: 
    services:
  app:
    image: alpine:3.20
    command: sleep infinity
    volumes:
      - data:/data
volumes:
  data:
    name: n2-shared-data
  2. In proja/: docker compose up -d && docker compose exec app sh -c 'echo important > /data/file' && docker compose down
  3. docker volume inspect -f '{{index .Labels "com.docker.compose.project"}}' n2-shared-data prints proja.
  4. In projb/: docker compose up -d, which prints the warning above (created for project "proja" (expected "projb")).
  5. In projb/: docker compose down -v prints Volume n2-shared-data Removed.
  6. proja's volume and its data are gone.
Compose Version
Docker Compose version 5.0.1
Docker Environment
Server Version: 29.1.3
Operating System: Docker Desktop
OSType: linux
Architecture: aarch64
Kernel Version: 6.12.54-linuxkit
Storage Driver: overlayfs
Anything else?

No response

Lingua principale
Go
Stelle
38.4k
Fork
5.9k
Merge medio
1g 17h
PR unite (30g)
69

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di docker/compose

Tutte le issue di docker/compose

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.