Fix Docker release runner provisioning #53
No reviewers
Labels
No labels
activitypub
actor
admin
ai-safety
article
articles
atproto
bug
cli
configuration
content
dev-environment
docker
enhancement
feature
federation
fediverse
forgejo
garage
health
how-to
logging
markdown
mastodon
media
navigation
opengraph
passkeys
preview
priority:medium
production
release
rendering
s3
settings
setup
status:active
status:done
status:inprogress
technical
webauthn
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
erik/slugkit.com!53
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/task-8a6810c6-release-bootstrap"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Slugkit.com release run 43 fails before checkout because
runs-on: dockerselects the unavailable local-onlyforgejo-runner-node20-docker:20260625image. On the same devserver runner, Erikvancraddock.com's Docker release run 80 successfully selectedubuntu-latest/ publicdocker.io/library/node:20-bookwormand installed Docker CLI and Buildx in the publishing workflow.Use that verified bootstrap path for Slugkit.com's normal release workflow. Install official Docker CLI/Buildx and check daemon/tool availability before tagging/building/publishing. This removes dependence on a manually provisioned local job image. Application source, publication credentials, multi-platform build, release tags and deployment remain unchanged. No container smoke/integration tests or testing runtime setup is added to CI/release workflows; the Docker setup is solely a publishing prerequisite.
Validation: bootstrap shell syntax, formatting and the full local pre-PR checks (352 tests) passed. Current-head PR CI and independent review are required before integration. The subsequent normal tag-triggered release will verify the repaired publishing path; no local/manual application publication is used.
Task: task-8a6810c6
Review update
ad7f6a645e7302ba11436564fe2d2033726b2e49.Acceptance criteria:
Next: integrate the approved workflow-only fix, retry publication through the normal tag-triggered release pipeline, and complete authorized GitOps rollout and deployed verification. Backup readiness is human-confirmed. Homelab diagnostic draft 161 was closed as superseded; no SSH/manual image repair is required for this pipeline fix.