feat: complete docker_publish skill — auth, DinD CI, E2E flow #26

Closed
opened 2026-02-26 04:46:54 +00:00 by mik-tf · 1 comment
Owner

Problem

The docker_publish skill had several gaps:

  • Interactive docker login (no FORGEJO_TOKEN automation)
  • CI workflow that would fail (no Docker-in-Docker, no BuildKit)
  • No end-to-end walkthrough from code to published container
  • No reference to a working implementation

Solution

  1. Registry Authentication — FORGEJO_TOKEN non-interactive login, local + CI, secret setup
  2. CI Workflow — Docker-in-Docker (docker:24-dind), BuildKit, official Docker actions, registry caching, SSH forwarding for private repos
  3. E2E Flow — local dev → CI automation → consuming published images
  4. Working Referencehero_services implements the full pipeline
  • env_secrets skill (canonical FORGEJO_TOKEN)
  • hero_docker packages docs
  • hero_services build-container.yaml (proven DinD implementation)
## Problem The `docker_publish` skill had several gaps: - Interactive `docker login` (no FORGEJO_TOKEN automation) - CI workflow that would fail (no Docker-in-Docker, no BuildKit) - No end-to-end walkthrough from code to published container - No reference to a working implementation ## Solution 1. **Registry Authentication** — FORGEJO_TOKEN non-interactive login, local + CI, secret setup 2. **CI Workflow** — Docker-in-Docker (`docker:24-dind`), BuildKit, official Docker actions, registry caching, SSH forwarding for private repos 3. **E2E Flow** — local dev → CI automation → consuming published images 4. **Working Reference** — `hero_services` implements the full pipeline ## Related - `env_secrets` skill (canonical FORGEJO_TOKEN) - [hero_docker packages docs](https://forge.ourworld.tf/lhumina_code/hero_docker/src/branch/development/docs/packages.md) - `hero_services` `build-container.yaml` (proven DinD implementation)
mik-tf changed title from feat: add automated Docker registry auth with FORGEJO_TOKEN to docker_publish skill to feat: complete docker_publish skill — auth, DinD CI, E2E flow 2026-02-26 05:03:30 +00:00
Author
Owner

The forge_docker_publish skill now covers all three gaps: non-interactive auth with FORGEJO_TOKEN, Podman-based CI (no Docker-in-Docker), and full E2E flow. Closing as completed.

The `forge_docker_publish` skill now covers all three gaps: non-interactive auth with FORGEJO_TOKEN, Podman-based CI (no Docker-in-Docker), and full E2E flow. Closing as completed.
Sign in to join this conversation.
No labels
No milestone
No project
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
lhumina_code/hero_skills#26
No description provided.