On Thu, 20 Feb 2025 at 11:11:15 +0800, Sean Whitton wrote:
> I would propose adding the following text to the manpage:
>
> You can simply run this command again to replace the image with one
> that's freshly built. Then use podman-image-prune(1) to clean up
> old images. See podman-container-prune(1) if you need to clean up
> containers that didn't shut down properly.
My concern about this is the last sentence, and whether it's sufficiently
clear to a podman beginner that for some non-autopkgtest use-cases,
this would be data loss. Because I know you're a schroot expert, I
can use an analogy: this is a bit like calling `schroot --end-session`
on every open session that has not been resumed since the last boot.
If your use-case is that container instances (~= sessions) are essentially
disposable anyway (as in autopkgtest and many schroot use-cases) then
that's fine, but if your use-case is that some container instances carry
important state (as they might when using toolbox(1) in particular),
then pruning stopped instances destroys that state. podman cannot tell
which way you plan to use it.
smcv
