KamoCRM

Cap BuildKit historia na tame mjenzi GC katika dockerd config

FixKlusterServices
Shipped
14 Novemba 2026, 21:43 UTC
Author
Kamo
Commit
18b221a

Pamoja na hakuna prune mbio, `docker rm` ya kumaliza CI kazi chombo bado alichukua 15-100 s: inasubiri kwa ajili ya kupita containerd GC (lease.Delete -> gcScheduler.ScheduleAndWait), na kila kupita alitumia wakati huo katika hatua alama (getMarked / scanRoots) kutembea metadata DB bloated na BuildKit kujenga historia kwamba ilikuwa kamwe kukata: moby_history uliofanyika 2,694 lease na 18,701 blobs nyuma kwa mwisho dockerd kuanza (2026-09-28), ~ 8x kila kitu kingine. - builder.history: maxAge 48h, maxEntries 100. - builder.gc: badala ya default 4-sheria sera (sheria #0 capped mitaa mazingira / cache mounts katika 2.57 GiB, kufuta cache baada ya kujenga) na moja ngumu backstop: max 80 GB cache, kukata wakati < 40 GB bure idle-dirisha k1m1-docker-prune.sh. Kutumia tu katika kimya CI dirisha: restarting docker pia huzuia forgejo-mshindi.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing