Skip to content

Conversation

@tico88612
Copy link
Contributor

@tico88612 tico88612 commented Nov 20, 2025

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update

Motivation and Context

Fixed #892

I'm a new contributor here. If there are any better ways to write it, please let me know.

Part of the function references content from PR #902. This PR will be rebased after that PR is merged.

Testing

  • Tested locally
  • Added/updated tests
  • Added/updated docs

@tico88612 tico88612 force-pushed the feat/container-prune branch 2 times, most recently from 104bdd2 to 589061e Compare November 20, 2025 18:21
@tico88612 tico88612 marked this pull request as ready for review November 20, 2025 18:22
@tico88612
Copy link
Contributor Author

cc @jglogan @realrajaryan

@saehejkang
Copy link
Contributor

This is also missing integration tests. Again, here is a good PR you can use to help make those.

@tico88612 tico88612 force-pushed the feat/container-prune branch from 589061e to 46d4018 Compare November 21, 2025 04:28
@tico88612
Copy link
Contributor Author

This is also missing integration tests. Again, here is a good PR you can use to help make those.

Uh, thanks. I just wonder how to write the testcase.

@tico88612 tico88612 force-pushed the feat/container-prune branch 5 times, most recently from 829c989 to 0f959a7 Compare November 21, 2025 15:57
@tico88612
Copy link
Contributor Author

Ok, testcases are ready.

@tico88612 tico88612 force-pushed the feat/container-prune branch from d6379bf to a327ffb Compare November 23, 2025 13:39
@saehejkang saehejkang mentioned this pull request Dec 3, 2025
7 tasks
@tico88612 tico88612 force-pushed the feat/container-prune branch from a327ffb to b50f515 Compare December 4, 2025 04:31
@saehejkang
Copy link
Contributor

After a lengthy discussion with maintainers, on #914, we are going to be focusing on refactoring any prune commands to take a client-side approach. Looks like you took a server-side approach (which is inherently not wrong), but this PR should be updated to reflect the new approach. Take a look at #914 and #940 for a template/reference. Feel free to ping me or the maintainers with any questions.

Signed-off-by: ChengHao Yang <17496418+tico88612@users.noreply.github.com>
Signed-off-by: ChengHao Yang <17496418+tico88612@users.noreply.github.com>
Signed-off-by: ChengHao Yang <17496418+tico88612@users.noreply.github.com>
Signed-off-by: ChengHao Yang <17496418+tico88612@users.noreply.github.com>
Signed-off-by: ChengHao Yang <17496418+tico88612@users.noreply.github.com>
@tico88612 tico88612 force-pushed the feat/container-prune branch from b50f515 to 8a28cd5 Compare December 13, 2025 16:54
@tico88612
Copy link
Contributor Author

Hi @jglogan @realrajaryan, could you take a look on this? I believe this's refactor prune commands to client-side approach.

@jglogan jglogan self-requested a review December 17, 2025 08:31
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.

[Request]: Storage - Add container prune command to remove stopped containers

2 participants