Default agent image is a private ghcr.io package no fresh install can pull #1711

Closed
opened 2026-10-29 12:24:29 +00:00 by sam · 1 comment
Owner

defaultContainerImage is still ghcr.io/samcharles93/archie-agent:latest
(internal/infrastructure/configuration/defaults.go:27). The repository is private, so
that package is private, so anything that has not already authenticated to ghcr.io
fails on its first task with an image pull error.

The deploy workflow already publishes to git.catlow.cloud/sam/archie-agent, written
into release.json, so the images exist on the new registry. What still says ghcr.io:
deployments/INSTRUCTIONS.md, deployments/single-forge-github.toml,
deployments/systemd-user-service.md, docker-compose.yml:98,
examples/profiles/Dockerfile.agent-net:6 and the config default above.

Decide whether the default points at the instance registry (makes a shipped default
instance-specific) or the agent image stays public on ghcr for other users.

`defaultContainerImage` is still `ghcr.io/samcharles93/archie-agent:latest` (internal/infrastructure/configuration/defaults.go:27). The repository is private, so that package is private, so anything that has not already authenticated to ghcr.io fails on its first task with an image pull error. The deploy workflow already publishes to `git.catlow.cloud/sam/archie-agent`, written into release.json, so the images exist on the new registry. What still says ghcr.io: deployments/INSTRUCTIONS.md, deployments/single-forge-github.toml, deployments/systemd-user-service.md, docker-compose.yml:98, examples/profiles/Dockerfile.agent-net:6 and the config default above. Decide whether the default points at the instance registry (makes a shipped default instance-specific) or the agent image stays public on ghcr for other users.
sam added the highbug labels 2026-10-29 12:24:29 +00:00
sam self-assigned this 2026-10-29 12:24:29 +00:00
Author
Owner

Verified fixed in the tree, no code left: commit 9d8f364a (2026-10-31) moved defaultContainerImage to the instance registry (internal/infrastructure/configuration/defaults.go:27) and rewrote every other surface the body names — deployments/INSTRUCTIONS.md, deployments/single-forge-github.toml, deployments/systemd-user-service.md, docker-compose.yml:98, examples/profiles/Dockerfile.agent-net:6, .github/workflows/deploy.yml:260. grep -rn ghcr.io over Go, YAML and Markdown now returns only test fixtures.

The failure the issue was actually about is gone too: an anonymous token request against the registry is issued for user -1 and returns the archie-agent:latest OCI index (2 platforms, HTTP 200) with no credentials, so a fresh install can pull it.

Closing against 9d8f364a.

Verified fixed in the tree, no code left: commit 9d8f364a (2026-10-31) moved `defaultContainerImage` to the instance registry (internal/infrastructure/configuration/defaults.go:27) and rewrote every other surface the body names — deployments/INSTRUCTIONS.md, deployments/single-forge-github.toml, deployments/systemd-user-service.md, docker-compose.yml:98, examples/profiles/Dockerfile.agent-net:6, .github/workflows/deploy.yml:260. `grep -rn ghcr.io` over Go, YAML and Markdown now returns only test fixtures. The failure the issue was actually about is gone too: an anonymous token request against the registry is issued for user -1 and returns the `archie-agent:latest` OCI index (2 platforms, HTTP 200) with no credentials, so a fresh install can pull it. Closing against 9d8f364a.
sam closed this issue 2026-11-07 15:54:47 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1711