feat(ci): add shadow-docker-build workflow for OS-49 Phase 3#964
Merged
feat(ci): add shadow-docker-build workflow for OS-49 Phase 3#964
Conversation
Signed-off-by: Jonas Toelke <jtoelke@nvidia.com>
This was referenced Apr 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add
.github/workflows/shadow-docker-build.yml— a dispatch-driven shadow ofdocker-build.ymlusing buildx's local driver (via the recently-mergedsetup-buildxdriver: local) and GHA cache (type=gha, scoped per(component, arch)). Proves Docker builds can run onnv-gha-runnerswithout reaching back to the in-cluster EKS BuildKit pods. Non-blocking;push: main+workflow_dispatchonly.Related Issue
OS-49 runner migration, Phase 3 / OS-127. This is PR 3 of the two-PR phase; PR 2 (setup-buildx driver input) already merged in #941.
Plan and decision thresholds live in OS-127 as an attached comment (Linear MCP
create_documentremains out of service).Changes
.github/workflows/shadow-docker-build.yml: new workflow.{gateway, supervisor, cluster} × {amd64, arm64}= 6 jobs.linux-{amd64,arm64}-cpu8(native per arch, no QEMU).ghcr.io/nvidia/openshell/ci:latestwith--privileged+ docker-socket mount — mirrorsdocker-build.yml../.github/actions/setup-buildxwithdriver: local.helm package deploy/helm/openshell -d deploy/docker/.build/charts/before the build (only onmatrix.component == 'cluster').docker buildx build --platform linux/<arch> --cache-from/--cache-to type=gha,scope=<component>-<arch>,mode=max --build-arg EXTRA_CARGO_FEATURES=openshell-core/dev-settings --load --file deploy/docker/Dockerfile.images --target <component>.docker buildx dufor cache-size visibility.Deliberate divergences from
docker-build.ymlAll per the OS-127 plan:
docker-build.ymlas a reusable workflow. Phase 6 folds the driver input into the reusable workflow; the shadow is self-contained.--push. Shadow measures build + cache mechanics, not publish.OPENSHELL_CARGO_VERSIONinjection. Binary will report0.0.0; wall-time unaffected.SCCACHE_MEMCACHED_ENDPOINT. Won't resolve off-EKS anyway; Dockerfile falls back to local disk cache.Risk note:
--privilegedon shared runnersnv-gha-runnersmay or may not permit--privilegedcontainers — this hasn't been confirmed. Per the OS-127 plan, the first dispatch is the test. If rejected, the job fails at container-start with an explicit policy error — clean failure, not partial execution. Phase 3 redesign would then consider non-DinD alternatives (docker-containerdriver in a sidecar, for instance). Same--privilegedpattern thatdocker-build.ymlon ARC uses daily.Testing
mise run pre-commit—main, unrelated to this PR. 8MD040errors inarchitecture/podman-rootless-networking.md(from PR Openshell driver podman #904's podman driver doc, landed today). Worth a separate tiny fix PR.gh workflow run shadow-docker-build.yml --ref main). First dispatch doubles as the--privileged-policy test.Checklist
create_documentoutage).