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

fix: adds --all to the volume prune command to prune named volumes #86

Merged
merged 1 commit into from
Sep 21, 2023

Conversation

sam-berning
Copy link
Contributor

see containerd/nerdctl@0844a51

Issue #, if available:

Description of changes:

CI was failing in finch and finch-core due to a named volume not getting cleaned up after bumping nerdctl to v1.6.0. turns out there was a change in behavior for the volume prune command.

Testing done:

Ran common-tests with @vsiravar and the volume tests succeeded

  • I've reviewed the guidance in CONTRIBUTING.md

License Acceptance

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@sam-berning sam-berning merged commit 4973e9f into runfinch:main Sep 21, 2023
sam-berning pushed a commit that referenced this pull request Sep 21, 2023
🤖 I have created a release *beep* *boop*
---


##
[0.7.5](v0.7.4...v0.7.5)
(2023-09-21)


### Bug Fixes

* adds --all to the volume prune command to prune named volumes
([#86](#86))
([4973e9f](4973e9f))
* Update logs test args
([#83](#83))
([011c2e3](011c2e3))


### Build System or External Dependencies

* **deps:** Bump github.com/onsi/ginkgo/v2 from 2.12.0 to 2.12.1
([#85](#85))
([89d408f](89d408f))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.

3 participants