From 530d374997b18b46965de4c93e86543e1d2b89f5 Mon Sep 17 00:00:00 2001 From: Mark Wielaard Date: Thu, 16 Jun 2022 23:18:43 +0200 Subject: [PATCH] README_containers: Document build --pull and system prune -a -f --- README_containers | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/README_containers b/README_containers index 66ac558..c414f72 100644 --- a/README_containers +++ b/README_containers @@ -69,8 +69,9 @@ Building the image ------------------ Note that the container files are rebuild once a week for the -builder.sourceware.org workers. So although unlikely it might be that -a freshly build container contains slightly newer versions of the +builder.sourceware.org workers (each Sunday the container builders run +docker system prune -a -f). So although unlikely it might be that a +freshly build container contains slightly newer versions of the packages than the one that ran on the builder.sourceware.org worker. The containers contain all build dependencies for all projects @@ -85,6 +86,10 @@ podman build -t builder-debian-stable \ -f builder/containers/Containerfile-debian-stable \ builder/containers +If you want to make sure you get the latest base image add --pull +which will attempt to pull a newer version of the image even if you +already got one locally. + Or use docker instead of podman, they take the same arguments (although the last PATH is optional in some versions). @@ -109,4 +114,7 @@ container and enter it as root: podman start debian-stable podman exec -it --user root debian-stable apt install emacs +After you are done you can reclaim all disk space used by the images +and containers by running: podman system prune -a -f + The same works with the docker command. -- 2.30.2