Repository navigation
github: honour LINUXKIT_PKG_ORG when exporting the EVE image from cache - #255
Conversation
The build-eve action and the riscv64 build step export the EVE image from the linuxkit cache under the hardcoded name lfedge/eve:<version>. When a runner sets LINUXKIT_PKG_ORG (e.g. to point linuxkit at a local registry namespace such as 10.208.13.77:5050/lfedge), linuxkit tags the built image under that org instead, and 'linuxkit cache export' fails with 'could not find image or index for docker.io/lfedge/eve:<version>' because the cache lookup is an exact-name match. Derive the org from LINUXKIT_PKG_ORG, falling back to lfedge, so the export asks for the name linuxkit actually wrote. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Paul Gaiduk <paulg@zededa.com>
|
Claude finished @europaul's task in 1m 29s —— View job Review: honour
|
Summary
lfedge/eve:<version>.LINUXKIT_PKG_ORG(our lab runners point it at the Zot registry namespace10.208.13.77:5050/lfedge) get the image tagged under that org, solinuxkit cache exportfails withcould not find image or index for docker.io/lfedge/eve:<version>. The cache lookup is an exact-name match on the stored reference.${LINUXKIT_PKG_ORG:-lfedge}so the export asks for the name linuxkit wrote. Unchanged behaviour where the variable is unset.Test plan
build.ymlon this PR: arm64eve (...)jobs on nanoforge get past the "Export docker container" step (they failed there in [DO NOT MERGE] pkg/uefi: force a rebuild (test authenticated git fetches) #254).eve (...)jobs likewise, if the Docker Hub login step passes on the kratos runners.Context: EV-2862 (replace local registries on kratos with Zot).
🤖 Generated with Claude Code