From 5780220ff193890d81f6aa868db41a922c495949 Mon Sep 17 00:00:00 2001 From: Bryan Van Deusen Date: Thu, 22 Oct 2026 10:20:33 -0400 Subject: [PATCH] The image build stops pruning the runner's shared Docker daemon The build job ran `docker system prune -af` on the runner's shared Docker daemon. That deletes every image no container is using at that moment, including images other repos' jobs had just pulled and were about to start. Jobs with a service container wait ~14s for it to become healthy between pull and create, and fail with "No such image" when a prune lands inside that wait (CI-runner #16). The runner host prunes nightly instead. Co-Authored-By: Claude Opus 5.5 --- .forgejo/workflows/ci.yml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/.forgejo/workflows/ci.yml b/.forgejo/workflows/ci.yml index e3825bc..3dc65bc 100644 --- a/.forgejo/workflows/ci.yml +++ b/.forgejo/workflows/ci.yml @@ -326,10 +326,10 @@ jobs: echo "value=$TAGS" >> $GITHUB_OUTPUT echo "build_version=$BUILD_VERSION" >> $GITHUB_OUTPUT - - name: Free disk space - run: | - docker system prune -af || true - docker builder prune --keep-storage 5g -f || true + # No disk-space prune step: the runner's Docker daemon is shared, and + # `docker system prune -af` here deleted images other repos' jobs had + # just pulled and were about to start (CI-runner #16). The runner host + # prunes nightly instead. # Bake EVERY client in, on every image build, so a self-hoster gets a working # app for their machine from the server holding their notes, with no trip to a