jlxq0/carddav-mcp
1
0
Fork 0
Code Issues 6 Pull requests 1 Projects Releases 4 Packages 1 Wiki Activity Actions

Release images are amd64-only #10

New issue
Open
opened 2026-08-26 04:58:31 +00:00 by jlxq0 · 0 comments
jlxq0 commented 2026-08-26 04:58:31 +00:00
Owner
Copy link

A note, not a task. Recording it because the answer is currently "correct by
accident of where it runs", and that is the kind of thing that surprises someone
later.

v0.1.3 publishes one runnable platform. The registry index for
forge.oddie.app/jlxq0/carddav-mcp:v0.1.3
(sha256:ccd22e91…) resolves to sha256:fb8f1018… for linux/amd64 plus one
unknown/unknown attestation manifest, and nothing else. v0.1.2 has the same
shape.

This is fine today: the fondue cluster is amd64 and the running pod
(carddav-mcp-7787f68774-6xbhx, container app) serves the amd64 digest.

It stops being fine if anyone wants to docker run the published image on an
Apple Silicon machine for local work, or if an arm64 node joins the cluster. In
both cases the failure is a pull-time no matching manifest rather than
anything the service can report about itself.

No requester. Do not build arm64 on the strength of this issue — a second
platform doubles the build and roughly doubles what Trivy has to scan per
release, for a machine nobody has yet named.

**A note, not a task.** Recording it because the answer is currently "correct by accident of where it runs", and that is the kind of thing that surprises someone later. `v0.1.3` publishes one runnable platform. The registry index for `forge.oddie.app/jlxq0/carddav-mcp:v0.1.3` (`sha256:ccd22e91…`) resolves to `sha256:fb8f1018…` for `linux/amd64` plus one `unknown/unknown` attestation manifest, and nothing else. `v0.1.2` has the same shape. This is fine today: the `fondue` cluster is amd64 and the running pod (`carddav-mcp-7787f68774-6xbhx`, container `app`) serves the amd64 digest. It stops being fine if anyone wants to `docker run` the published image on an Apple Silicon machine for local work, or if an arm64 node joins the cluster. In both cases the failure is a pull-time `no matching manifest` rather than anything the service can report about itself. **No requester. Do not build arm64 on the strength of this issue** — a second platform doubles the build and roughly doubles what Trivy has to scan per release, for a machine nobody has yet named.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
docs/mergeable-is-async
v0.1.6
v0.1.5
v0.1.4
v0.1.3
v0.1.2
v0.1.1
v0.1.0
Labels
Clear labels   
waiting-on-julian
Blocked on Julian. The ask is in the issue.

No labels
waiting-on-julian
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
jlxq0/carddav-mcp#10
No description provided.