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.

Sign up for GitHub

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

Jump to bottom

Named volumes not getting removed correctly in docker-compose 2.0 #106

Closed
nguyer opened this issue Oct 6, 2021 · 0 comments · Fixed by #107
Closed

Named volumes not getting removed correctly in docker-compose 2.0 #106

nguyer opened this issue Oct 6, 2021 · 0 comments · Fixed by #107
Assignees
@nguyer
Labels
bug Something isn't working

Comments

@nguyer
Copy link
Contributor

nguyer commented Oct 6, 2021

Previously, if a named volume was created before running docker-compose up it would still be removed when running docker-compose down --volumes. In docker-compose 2.0.x this no longer appears to be the case. This causes all kinds of problems and confusion when the CLI reports that it has rolled changes back, but leftover volumes still have old data on them, causing subsequent runs to fail.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nguyer nguyer

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixes for docker-compose 2.0 compatibility hyperledger/firefly-cli
1 participant
@nguyer