Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

COMPOSE_REMOVE_ORPHANS can be set to always apply --remove-orphans #9200

Merged
merged 1 commit into from
Feb 23, 2022

Conversation

ndeloof
Copy link
Contributor

@ndeloof ndeloof commented Feb 23, 2022

What I did
--remove-orphans default value is computed based on COMPOSE_REMOVE_ORPHANS env variable

Related issue
closes #9199

(not mandatory) A picture of a cute animal, if possible in relation with what you did

Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
Copy link
Contributor

@glours glours left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@glours glours merged commit fd676ad into docker:v2 Feb 23, 2022
@nickjj
Copy link

nickjj commented Feb 23, 2022

That was the fastest issue -> merged PR ever, thanks a lot!

@ndeloof ndeloof deleted the COMPOSE_REMOVE_ORPHANS branch December 20, 2023 13:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Feature request: Add COMPOSE_REMOVE_ORPHANS to let us default to --remove-orphans on a per project basis
3 participants