containers / containers/toolbox
Removal of a Toolbox image from which are derived Toolbox containers made a one-step operation
- Dominant language
- Go
- Stars
- 3.5k
- Forks
- 262
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 1
Description
**Problem description**
Hello. Removal of a _Toolbox_ image from which are derived _Toolbox_ containers is a two-step operation.
'`toolbox rm && toolbox rmi `'
Attempt as a one-step operation
```
$ toolbox rmi
Error: image has dependent children
```
_goal_: Avoiding the unnecessary print of an error message by offering the possibility to make the removal a one-step operation.
**Solution description**
Removal of a _Toolbox_ image from which are derived _Toolbox_ containers made a one-step operation.
Suggested interactive output:
```
$ toolbox rmi
Image has dependent children that must be removed first in order to remove the image.
##IDs of containers derived from the image:##
####
Do you want to remove these containers? [N/y]:
```
**Alternatives I have considered**
Such removal in Podman is a two-step operation as well. I wish it was an alternative.
Contributor guide
Research direction
Start at the implementation of the `toolbox rmi` command and compare it with the existing `toolbox rm` behavior. Trace how dependent containers are identified and how the current error is reported. Done means `toolbox rmi` can offer interactive removal of the listed dependent containers before removing the image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100