# Self-Healing CI: Missing System Packages and Setup Gaps

> A missing system library or tool fails the build until someone installs it. See the manual fix and how self-healing CI installs it and proposes a durable change.

Source: https://latchkey.dev/learn/self-healing-ci/self-heal-missing-system-package  
Updated: 2026-06-25

When a build fails because a system package or tool is missing, the fix is mechanical: install it - and, ideally, bake it into the setup so it never recurs.

## 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: missing system packages and setup gaps?

A step fails with command not found or a missing shared library. The code is fine; the runner just does not have a required tool or -dev package installed. A human adds an install step and the build passes.

### How do I fix Self-Healing CI: missing system packages and setup gaps manually?

[object Object]

### Can Self-Healing CI: missing system packages and setup gaps be fixed automatically?

Because the missing piece is named in the error and the remedy is a well-scoped install, this can be automated safely from a curated allowlist of known-safe packages. A self-healing pipeline installs the missing dependency, retries the step, and can propose a durable change to your setup so the gap is closed for good - turning 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