system/deployment/2_Image_Building.md

@@ -25,8 +25,7 @@ docker image ls
 docker image rm exampleimageid1 exampleimageid2 exampleimageid3 […]
 # e. g. with IMAGE_IDs:
 docker image rm ba53dde63be9 9a9381a088dd b5040966bef3 cc2f61dbdae0 […]
-# prune docker build cache
-docker builder prune
+# Prune docker build cache
 docker buildx prune
 ```
 
@@ -67,4 +66,10 @@ docker image tag "reseed-workers:latest" "reseed-workers:${DOCKER_IMAGE_TAG}"
 
 ℹ Tagging the images as `latest` on the builder VM makes life easier when exporting/copying them over to the actual ReSeeD VM on which they will run, because this eliminates the need for one error-prone "copy $DOCKER_IMAGE_TAG string to another machine" operation.
 
+⚠️ Make sure to prune the build cache again after building the images to prevent the filesystem from running out of space (the build process can easily cache GBs of storage space each time the images are built):
+```
+# Prune docker build cache
+docker buildx prune
+``` 
+
 Transfer the container images to the desired ReSeeD / docker host as described on the ["Transferring Images" page](/system/deployment/3_Transferring_Images).