It would be helpful to have an procedure execution option for Batch Prune System
For example, If I have a procedure to do a batch pull and batch deploy if changed, it would be helpful to have a batch prune system stage at the end to clean everything up.
Originally created by @seansheep on GitHub (Jul 10, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/655
It would be helpful to have an procedure execution option for **Batch Prune System**
For example, If I have a procedure to do a **batch** pull and **batch deploy if changed**, it would be helpful to have a **batch prune system** stage at the end to clean everything up.
Per docker system prune:
Remove all unused containers, networks, images (both dangling and unused), and optionally, volumes.
It would be equivalent of setting a procedure execution stage of "Prune System" except currently you can only select a single server to run the stage on. Other options (like Batch Pull Stack) you can specify a regex for all stacks that you want the operation to run on. It would be good if you could specify a regex for which servers to run it on, like the other batch commands.
<!-- gh-comment-id:3060512371 -->
@seansheep commented on GitHub (Jul 11, 2025):
Per [docker system prune](https://docs.docker.com/reference/cli/docker/system/prune/):
Remove all unused containers, networks, images (both dangling and unused), and optionally, volumes.
It would be equivalent of setting a procedure execution stage of "Prune System" except currently you can only select a single server to run the stage on. Other options (like Batch Pull Stack) you can specify a regex for all stacks that you want the operation to run on. It would be good if you could specify a regex for which servers to run it on, like the other batch commands.
Further request to include an option to exclude specific images defined by their names.
There'd be images that we occasionally use that we do not want to pull every time, when its related containers run. And we don't want the generic 'Batch Prune Images' or even the 'Prune Images' procedures to prune them.
I've miserably failed to create an action using PruneImages execute API but since it doesn't accept any other parameter but 'server', it's futile.
For now, I'm using DeleteImage Execute API with a custom coded Actions which use a pre-defined list of images per server to exclude from the deletion. These Action are invoked at the end via "Batch Run Action", after the built-in "Batch Pull Stack" runs followed by "Deploy Stack if changed".
<!-- gh-comment-id:3317012375 -->
@dpurnam commented on GitHub (Sep 22, 2025):
Further request to include an option to exclude specific images defined by their names.
There'd be images that we occasionally use that we do not want to pull every time, when its related containers run. And we don't want the generic 'Batch Prune Images' or even the 'Prune Images' procedures to prune them.
~~I've miserably failed to create an action using PruneImages execute API but since it doesn't accept any other parameter but 'server', it's futile.~~
For now, I'm using DeleteImage Execute API with a custom coded Actions which use a pre-defined list of images per server to exclude from the deletion. These Action are invoked at the end via "Batch Run Action", after the built-in "Batch Pull Stack" runs followed by "Deploy Stack if changed".
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @seansheep on GitHub (Jul 10, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/655
It would be helpful to have an procedure execution option for Batch Prune System
For example, If I have a procedure to do a batch pull and batch deploy if changed, it would be helpful to have a batch prune system stage at the end to clean everything up.
@mbecker20 commented on GitHub (Jul 10, 2025):
What does it prune?
@seansheep commented on GitHub (Jul 11, 2025):
Per docker system prune:
Remove all unused containers, networks, images (both dangling and unused), and optionally, volumes.
It would be equivalent of setting a procedure execution stage of "Prune System" except currently you can only select a single server to run the stage on. Other options (like Batch Pull Stack) you can specify a regex for all stacks that you want the operation to run on. It would be good if you could specify a regex for which servers to run it on, like the other batch commands.
@mbecker20 commented on GitHub (Jul 11, 2025):
Oh I see what you mean now
@dpurnam commented on GitHub (Sep 22, 2025):
Further request to include an option to exclude specific images defined by their names.
There'd be images that we occasionally use that we do not want to pull every time, when its related containers run. And we don't want the generic 'Batch Prune Images' or even the 'Prune Images' procedures to prune them.
I've miserably failed to create an action using PruneImages execute API but since it doesn't accept any other parameter but 'server', it's futile.For now, I'm using DeleteImage Execute API with a custom coded Actions which use a pre-defined list of images per server to exclude from the deletion. These Action are invoked at the end via "Batch Run Action", after the built-in "Batch Pull Stack" runs followed by "Deploy Stack if changed".