Package: autopkgtest Version: 5.44 Severity: wishlist X-debbugs-cc: ijack...@chiark.greenend.org.uk
Dear maintainer,
autopkgtest-build-podman(1) describes creating a container image
suitable for testing uploads targeting Debian unstable, from scratch,
like this:
mmdebstrap --variant=minbase sid - \
| autopkgtest-build-podman --release=sid --tarball=-
This is sufficient for 'autopkgtest-virt-podman sid' to allow you to
speak the autopkgtest protocol with a fresh environment, which is great.
(The context, as you have perhaps guessed, is tag2upload, where our
source package building tool uses the autopkgtest protocol to work in a
clean environment.)
However, there are no instructions about maintaining the container image
and the image store. In particular:
1. How does one rebuild the image, say in a weekly cronjob? Do you just
run the same command again, and the new image will take precedence?
2. How do you prune ~/.local/share/containers/ to avoid it just building
up forever?
I found both 'podman image prune' and 'podman container prune'.
It would be great if a recommendation could be documented.
We can resort to just 'rm -rf ~/.local/share/containers' but that has
the disadvantage of service downtime while the new image is built.
Thanks.
--
Sean Whitton
signature.asc
Description: PGP signature
