You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "TingYao Huang (Jira)" <ji...@apache.org> on 2026/09/21 16:53:00 UTC
[jira] [Resolved] (YUNIKORN-3466) Reproducible build fails under podman due to unqualified golang image
[ https://issues.apache.org/jira/browse/YUNIKORN-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
TingYao Huang resolved YUNIKORN-3466.
-------------------------------------
Fix Version/s: 1.11.0
Target Version: 1.11.0
Resolution: Fixed
> Reproducible build fails under podman due to unqualified golang image
> ---------------------------------------------------------------------
>
> Key: YUNIKORN-3466
> URL: https://issues.apache.org/jira/browse/YUNIKORN-3466
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
> Reporter: TingYao Huang
> Assignee: weichen lai
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
>
> h3. Problem
> The reproducible build path in the k8shim Makefile runs a golang container using an unqualified short name:
> {code:java}
> $(DOCKER) run -t --rm=true --volume "$(DOCKER_BUILDROOT):/buildroot" \ "golang:$(GO_REPRO_VERSION)" sh -c "..." {code}
> Docker's daemon transparently prepends "docker.io/library/" to unqualified image names, so this has worked historically. Podman does not do this: with short-name-mode=enforcing (the default on Fedora, RHEL, and recent Ubuntu releases) and no TTY, short-name resolution fails and the build aborts.
> h3. Why this surfaces now
> The reproducible build path is only entered when REPRO=1. The existing consumers do not set it: * {{make kind-e2e}} (covered by YUNIKORN-3441) uses the non-repro branch, so podman support merged there without hitting this. * However, {{build-image.py}} in yunikorn-release (YUNIKORN-3443) hard-codes REPRODUCIBLE_BUILDS=1. Once that PR is merged, podman-based release builds will always trigger this path and fail.
> The REPRODUCIBLE_BUILDS=1 path mounts the repo into the container and runs go build as root. Since Go 1.18, go build does VCS stamping via git, which fails with detected dubious ownership in repository when the container's root UID doesn't own the mounted .git (host-owned).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org