Skip to content

feat(docker-publish): support self-hosted runners, private repos and build-only runs - #63

Merged
JustMaris merged 1 commit into
mainfrom
feat/docker-publish-self-hosted
Oct 4, 2026
Merged

JustMaris merged 1 commit into
mainfrom
feat/docker-publish-self-hosted

Conversation

@JustMaris

Copy link
Copy Markdown
Member

Extends docker-publish.yml so the two private image builds can use it: slovy-py (2 Dockerfiles, built on PRs without pushing) and Mystery-Game (2 targets of one Dockerfile), both on oracle-x64.

  • New inputs: file, target, push (default true; false builds without pushing or attesting).
  • On a self-hosted runner, set automatically:
    • driver: docker, so the layer cache stays on the VM
    • provenance: false, because dockerd's builder can't store buildx's provenance manifest
    • the same capped cleanup the callers run today (buildx prune --max-used-space 20GB)
  • Private repos: the attestation step is skipped, since artifact attestations need GitHub Enterprise Cloud for private repositories.
  • Existing callers: hosted, public, defaults. They behave exactly as before.
  • The README documents the new inputs, the one-platform limit of the self-hosted builder, and that callers still grant the full permission set.

actionlint and zizmor (offline) are clean locally.

@JustMaris
JustMaris enabled auto-merge (squash) October 4, 2026 16:53
@JustMaris
JustMaris merged commit 9a103ff into main Oct 4, 2026
10 checks passed
@JustMaris
JustMaris deleted the feat/docker-publish-self-hosted branch October 4, 2026 16:54
@dnb-robot dnb-robot Bot mentioned this pull request Oct 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant