[STORY] Package ripwire into the Foreman coder image and the macOS agent install

Open
#1,903 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@Defilan is already working on this.

Since Sep 26, 2026.

  • #1907 by @Defilan — closed without merging

Assessment

This issue has not been assessed yet.

Description

area/foreman component/metal-agent docker size/medium

Goal

ripwire is present and pinned on every host that runs a Foreman coder agent, in both the container and the macOS channels, with its license and notices shipped.

Definition of done

The observable that proves it is done, and its negative.

  • Observable: a coder Job pod on the foreman coder image runs ripwire --version successfully; a launchd-installed foreman-agent on macOS resolves the same pinned binary.
  • Negative: if the pinned version or checksum changes, the image/macOS build must FAIL (the pin is enforced, not decorative).

Scope

What changes, by file or area.

  • Dockerfile.foreman-agent-builder: pinned fetch of the ripwire release for ${TARGETARCH} (linux amd64/arm64), SHA-256 verified, into /usr/local/bin/ripwire; LICENSE + THIRD_PARTY.md copied to /licenses/ripwire/. Mirrors the existing helm/golangci-lint pin blocks.
  • Makefile install-foreman-agent (:324): fetch and stage the pinned darwin arm64 binary into the versioned install layout; the launchd plist resolves it (PATH or an env var).
  • charts/foreman/values.yaml: document the image/version knobs; pass-through only.
  • A third-party attribution doc (new docs/ page): version pin, license, vendored-license set.

Out of scope

What this story deliberately does not do, so the work does not creep.

  • Any code that calls ripwire (that is the advisory backend and tool stories).

Consumers and surfaces touched

Every resource, endpoint, port, wire payload, command-line contract, or CRD field this touches, and what must stay true for its consumer. Write "none" for a pure docs change.

  • The foreman coder image (ghcr.io/defilantech/llmkube-foreman-agent-coder) and the macOS install layout. The image's Trivy release scan now covers the ripwire binary, so a ripwire CVE can block a release.

Verification

The exact commands that must pass, and the expected result.

make docker-build-foreman-agent-builder
docker run --rm <img> ripwire --version   # prints the pinned version
make install-foreman-agent FOREMAN_INSTALLED_MODELS=test   # stages ripwire

Falsification

The production edit that must make a test or check fail, and the failure you expect to see. If you cannot name one, the verification does not bite.

  • Edit: change the pinned SHA-256 to a wrong value.
  • Expected failure: the image build fails at the checksum step.

Risks

What could go wrong, and the unknowns worth calling out before building.

  • 50 MB image growth; new CVE surface scanned on every release; the macOS channel is a second trust surface.
  • ripwire's licenses are permissive (Apache-2.0 plus MIT/zlib/Unicode-DFS-2016 vendors) but must be shipped, and this is llmkube's first third-party attribution.
Dominant language
Go
Stars
232
Forks
37
Avg merge
21h 42m
Merged PRs (30d)
244

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from defilantech/LLMKube

All issues in defilantech/LLMKube

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.