service/ci.md

@@ -234,21 +234,21 @@ normally [purged regularly](#image-volume-and-container-storage-and-caching) but
 might use up too much space all of a sudden.
 
 To diagnose this issue better, you can see the running containers
-with:
+with (as the `gitlab-runner` user):
 
-    docker ps
+    podman ps
 
 ... and include stopped or dead containers with:
 
-    docker ps -a
+    podman ps -a
 
 Images are visible with:
 
-    docker images
+    podman images
 
 And volumes with:
 
-    docker volume ls
+    podman volume ls
 
 ... although that output is often not very informative because GitLab
 runner uses volumes to cache data and uses opaque volume names.
@@ -258,13 +258,20 @@ rm` (for containers), `docker image rm` (for images) and `docker
 volume rm` (for volumes). But usually, you should probably just run
 the cleanup jobs by hand, in order:
 
-    docker system prun --filter until=72h
+    podman system prune --filter until=72h
 
-The time frame can be lowered for a more aggressive cleanup.
+The time frame can be lowered for a more aggressive cleanup. Volumes
+can be cleaned with:
 
-Alternatively, this will also clean old containers:
+    podman system prune --volumes
 
-    /usr/local/sbin/tpo-docker-clean-cache
+And images can be cleaned with:
+
+    podman system prune --force --all --filter until=72h
+
+Those commands mostly come from the `profile::podman::cleanup` class,
+which might have other commands already. Other cleanup commands are
+also set in `profile::gitlab::runner::docker`.
 
 The `tpa-du-gl-volumes` script can also be used to analyse which
 project is using the most disk space: