Skip to content

[BUG] v2.23.0 broke docker-compose down -v --remove-orphans NAME ? #11203

@ValiDrv

Description

@ValiDrv

Description

I have a docker-compose.yml file with multiple common services, db, redis, proxies, etc, referenced to via depends_on, and a few main services, web1, web2, etc.

After starting all services correctly, if I try to bring one service down using:
docker-compose down -v --remove-orphans web1

With version v2.23.0 and up, it will bring down all services listed in the docker-compose file (including web2, the common services, etc)

With version v2.22.0 and bellow, it will bring down only the expected service web1, and any other service which is not being depended on.

Is this an expected behaviour? or a bug which was introduced via v2.23.0 with the profile updates?

Steps To Reproduce

No response

Compose Version

Docker Compose version v2.23.1 - bug
Docker Compose version v2.23.0 - bug
Docker Compose version v2.22.0 - works
Docker Compose version v2.20.0 - works

Docker Environment

Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.3 LTS
Release:	22.04
Codename:	jammy


Client:
 Version:    24.0.5
 Context:    default
 Debug Mode: false
 Plugins:
  compose: Docker Compose (Docker Inc.)
    Version:  v2.2.3
    Path:     /root/.docker/cli-plugins/docker-compose

Anything else?

No response

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions