Skip to content

ci: prune stale earthly buildkit cache on self-hosted host #1665

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
skylar-simoncelli wants to merge 4 commits into
base: main
Choose a base branch
from
Open

ci: prune stale earthly buildkit cache on self-hosted host #1665

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d429bd0
ci: prune stale earthly buildkit cache on self-hosted host
skylar-simoncelli Jun 9, 2026
1f52323
Merge branch 'main' into skylar/ci-prune-earthly-buildkit-cache
justinfrevert Jun 11, 2026
32335a9
Merge branch 'main' into skylar/ci-prune-earthly-buildkit-cache
skylar-simoncelli Jun 11, 2026
d8a7371
Merge branch 'main' into skylar/ci-prune-earthly-buildkit-cache
skylar-simoncelli Jun 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions .github/workflows/continuous-integration.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1167,6 +1167,24 @@ jobs:
docker volume ls -q --filter "label=com.docker.compose.project=${proj}" \
| xargs -r docker volume rm -f || true

# Bound the shared earthly-buildkitd cache. It accumulates pulled base
# images and cache mounts (e.g. nixos/nix for compactc) across all slots
# on the self-hosted host, and is NOT covered by the local-env teardown
# above. Left unbounded it creeps toward the 1.7 TB /var ceiling and large
# link steps die with "No space left on device". buildctl prune is
# concurrency-safe (it skips records held by in-flight builds), and
# --keep-duration keeps a day of hot cache so other PRs still hit it. This
# does not change the daemon's settings hash, so it never restarts the
# shared buildkitd. The host-side reaper timer (shielded-iac runner role)
# is the backstop for slots whose job is hard-killed before this runs.
- name: Prune stale earthly buildkit cache (defensive)
if: always()
shell: bash
run: |
if docker inspect earthly-buildkitd >/dev/null 2>&1; then
docker exec earthly-buildkitd buildctl prune --keep-duration=24h || true
Comment thread
skylar-simoncelli marked this conversation as resolved.

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 12, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Point buildctl at the TCP daemon

On self-hosted runs where Earthly manages earthly-buildkitd with TCP transport (the repo’s self-hosted config disables TLS for that shared daemon), this docker exec invokes buildctl without --addr/BUILDKIT_HOST, so it falls back to the default Unix socket inside the container instead of the daemon’s TCP listener. The prune then fails and || true hides it, leaving the shared cache unbounded in exactly the disk-pressure scenario this step is meant to fix; pass the daemon address explicitly (for example the container-local TCP endpoint). Fresh evidence: the current .earthly/config.selfhosted.yml still configures the shared no-TLS Earthly daemon, while the added command still relies on buildctl defaults.

Useful? React with 👍 / 👎.

fi

- uses: ./.github/actions/tree-cache-guard/save
if: steps.guard.outputs.hit != 'true'
with:
Expand Down
Loading