mmintel/at-mintel
1
0
Fork 0
Code Issues Pull Requests 4 Actions Packages Projects Releases Wiki Activity

fix: clean buildx caches and dangling builder volumes #1

Open
mmintel wants to merge 0 commits from fix-docker-prune-buildkit into main
pull from: fix-docker-prune-buildkit
merge into: mmintel:main
Conversation 0 Commits - Files Changed -
mmintel commented 2026-06-03 14:46:55 +00:00
Owner
Copy Link

Die Server laufen durch Docker Buildkit State Volumes (buildx_buildkit_builder-*_state) voll, weil diese von docker volume prune ignoriert werden, solange noch gestoppte oder verwaiste Build-Container existieren.

Dieser Fix:

  1. Löscht explizit alle buildx_buildkit_builder Container, bevor der Volume Prune startet.
  2. Führt einen sauberen docker buildx prune -af aus.
  3. Greift notfalls hart durch, um verwaiste Buildkit-Volumes radikal zu entfernen.

Damit sind die "No space left on device" (z.B. bei Gitea / Listmonk) Geschichte.

Die Server laufen durch Docker Buildkit State Volumes (buildx_buildkit_builder-*_state) voll, weil diese von `docker volume prune` ignoriert werden, solange noch gestoppte oder verwaiste Build-Container existieren. Dieser Fix: 1. Löscht explizit alle `buildx_buildkit_builder` Container, bevor der Volume Prune startet. 2. Führt einen sauberen `docker buildx prune -af` aus. 3. Greift notfalls hart durch, um verwaiste Buildkit-Volumes radikal zu entfernen. Damit sind die "No space left on device" (z.B. bei Gitea / Listmonk) Geschichte.
mmintel added 1 commit 2026-06-03 14:46:55 +00:00
fix: clean buildx caches and dangling builder volumes in mintel-optimizer
All checks were successful
Monorepo Pipeline / ⚡ Prioritize Release (push) Successful in 7m37s
Details
Monorepo Pipeline / 🧪 Test (push) Successful in 1m27s
Details
Monorepo Pipeline / 🏗️ Build (push) Successful in 3m33s
Details
Monorepo Pipeline / 🧹 Lint (push) Successful in 4m10s
Details
Monorepo Pipeline / 🚀 Release (push) Has been skipped
Details
Monorepo Pipeline / 🐳 Build Gatekeeper (Product) (push) Has been skipped
Details
Monorepo Pipeline / 🐳 Build Build-Base (push) Has been skipped
Details
Monorepo Pipeline / 🐳 Build Production Runtime (push) Has been skipped
Details
0fc4ddbc28
All checks were successful
Monorepo Pipeline / ⚡ Prioritize Release (push) Successful in 7m37s
Details
Monorepo Pipeline / 🧪 Test (push) Successful in 1m27s
Details
Monorepo Pipeline / 🏗️ Build (push) Successful in 3m33s
Details
Monorepo Pipeline / 🧹 Lint (push) Successful in 4m10s
Details
Monorepo Pipeline / 🚀 Release (push) Has been skipped
Details
Monorepo Pipeline / 🐳 Build Gatekeeper (Product) (push) Has been skipped
Details
Monorepo Pipeline / 🐳 Build Build-Base (push) Has been skipped
Details
Monorepo Pipeline / 🐳 Build Production Runtime (push) Has been skipped
Details
This branch is already included in the target branch. There is nothing to merge.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin fix-docker-prune-buildkit:fix-docker-prune-buildkit
git checkout fix-docker-prune-buildkit
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
mmintel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mmintel/at-mintel#1
Delete Branch "fix-docker-prune-buildkit"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?