# Self-Healing CI: Automatic Recovery from "No Space Left on Device"

> Disk-exhaustion failures are recoverable without a code change. See the manual cleanup and how self-healing CI reclaims space and retries automatically.

Source: https://latchkey.dev/learn/self-healing-ci/self-heal-disk-full-no-space  
Updated: 2026-06-25

Running out of disk is one of the most recoverable CI failures there is: the fix is to reclaim space and try again, with no change to your code.

## What makes a failure safely retryable

Automatic retry is only correct for failures that are genuinely transient. Retrying a deterministic failure wastes minutes and hides a real defect, so the classification matters more than the retry mechanism.

- Safe to retry: network timeouts, registry 5xx, transient DNS failures, a service container that was not ready, a spot instance reclaimed mid-run.
- Not safe to retry: assertion failures, compile errors, lint violations, anything that fails identically on every attempt.
- Ambiguous, and worth investigating rather than retrying: out-of-memory kills, disk exhaustion, and flaky tests. These repeat under load and a retry only hides the trend.
- Always record that a retry happened. A pipeline that silently retries is a pipeline whose real failure rate you do not know.

## FAQ

### What causes Self-Healing CI: automatic recovery from "No space left on Device"?

A build fails with no space left on device. The runner filled up with image layers, caches, and temporary files. Someone adds a cleanup step or re-runs on a fresh runner, and the build passes unchanged.

### How do I fix Self-Healing CI: automatic recovery from "No space left on Device" manually?

[object Object]

### Can Self-Healing CI: automatic recovery from "No space left on Device" be fixed automatically?

Because the trigger (a disk-space error) and the remedy (reclaim space, then retry) are both well-defined, this class of failure can be handled with no human involvement. A self-healing pipeline detects the disk-exhaustion condition, frees space on the runner using safe cleanup, retries the step, and - where appropriate - suggests a

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt