-
Notifications
You must be signed in to change notification settings - Fork 609
cli: add --all-inactive for rm command #885
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
Conversation
398314a to
a1dbc8a
Compare
commands/rm.go
Outdated
| flags := cmd.Flags() | ||
| flags.BoolVar(&options.keepState, "keep-state", false, "Keep BuildKit state") | ||
| flags.BoolVar(&options.keepDaemon, "keep-daemon", false, "Keep the buildkitd daemon running") | ||
| flags.BoolVar(&options.inactive, "inactive", false, "Remove inactive builders") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer all-inactive that makes it clear that this is a different mode
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree but more generally I think the CLI has a confusing design for some commands. For example the following would make more sense:
docker buildx du>docker buildx cache dudocker buildx prune>docker buildx cache prunedocker buildx rm --all-inactive>docker buildx prune
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using prune for something other than build cache is quite confusing imho. Especially because it means completely different thing atm. For the possibility of cache subcommand we can discuss in another issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using
prunefor something other than build cache is quite confusing imho.
Yes can be confusing.
For the possibility of cache subcommand we can discuss in another issue.
👍
a1dbc8a to
519f73b
Compare
519f73b to
2f54a85
Compare
8e3dcb7 to
90163ed
Compare
Signed-off-by: CrazyMax <[email protected]>
90163ed to
378f0b4
Compare
fixes #851
Add
--inactiveto be able to remove nodes that are not in running state. This will also remove builders that don't have any node left available after the process.Signed-off-by: CrazyMax [email protected]