PerishFire/images
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

feat: carry the Docker and Helm clients #1

Merged
PerishFire merged 1 commit from land/task/forge-projection-clients into main 2026-08-16 16:27:02 +00:00
Conversation 0 Commits 1 Files changed 4 +44 -5
PerishFire commented 2026-08-16 15:58:33 +00:00
Owner
Copy link

feat: carry the Docker and Helm clients

The release lane could not project an image or a chart from any product,
and the reason was not configuration. plumb ship oci build runs docker build and plumb ship chart package runs helm package, while the job
that would run them executes inside this image, which carried neither. A
product declaring [release.oci] therefore passed its own doctor and then
had nowhere to be built; the medium was undeclarable rather than merely
unconfigured.

The clients arrive the way every other tool here does. Docker comes from
the pinned docker:27-cli stage this repository already trusts in its own
workflows, and its binary is static, so a Debian base runs it unchanged.
Helm comes from a release tarball pinned by version and SHA-256, checked
before it is unpacked.

They are clients and nothing more. The image carries no daemon and no
cluster, so a job that projects onto those media supplies its own endpoint
and credentials, exactly as this repository's own lanes already do with
DOCKER_HOST. The guard proves the clients run and that helm package
and helm push answer, which is the whole of the claim.

Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com

feat: carry the Docker and Helm clients The release lane could not project an image or a chart from any product, and the reason was not configuration. `plumb ship oci build` runs `docker build` and `plumb ship chart package` runs `helm package`, while the job that would run them executes inside this image, which carried neither. A product declaring `[release.oci]` therefore passed its own doctor and then had nowhere to be built; the medium was undeclarable rather than merely unconfigured. The clients arrive the way every other tool here does. Docker comes from the pinned `docker:27-cli` stage this repository already trusts in its own workflows, and its binary is static, so a Debian base runs it unchanged. Helm comes from a release tarball pinned by version and SHA-256, checked before it is unpacked. They are clients and nothing more. The image carries no daemon and no cluster, so a job that projects onto those media supplies its own endpoint and credentials, exactly as this repository's own lanes already do with `DOCKER_HOST`. The guard proves the clients run and that `helm package` and `helm push` answer, which is the whole of the claim. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
feat: carry the Docker and Helm clients
All checks were successful
guard / images (push) Successful in 16s
Details
3a79a25c77 
feat: carry the Docker and Helm clients

The release lane could not project an image or a chart from any product,
and the reason was not configuration. `plumb ship oci build` runs `docker
build` and `plumb ship chart package` runs `helm package`, while the job
that would run them executes inside this image, which carried neither. A
product declaring `[release.oci]` therefore passed its own doctor and then
had nowhere to be built; the medium was undeclarable rather than merely
unconfigured.

The clients arrive the way every other tool here does. Docker comes from
the pinned `docker:27-cli` stage this repository already trusts in its own
workflows, and its binary is static, so a Debian base runs it unchanged.
Helm comes from a release tarball pinned by version and SHA-256, checked
before it is unpacked.

They are clients and nothing more. The image carries no daemon and no
cluster, so a job that projects onto those media supplies its own endpoint
and credentials, exactly as this repository's own lanes already do with
`DOCKER_HOST`. The guard proves the clients run and that `helm package`
and `helm push` answer, which is the whole of the claim.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Land-Source: task/forge-projection-clients@1c180f5aa3
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
PerishFire/images!1
No description provided.