Skip to content

Fix operator image build failure when using Podman as container runtime#1976

Open
fjglira wants to merge 1 commit into
istio-ecosystem:mainfrom
fjglira:fix-podman-build
Open

Fix operator image build failure when using Podman as container runtime#1976
fjglira wants to merge 1 commit into
istio-ecosystem:mainfrom
fjglira:fix-podman-build

Conversation

@fjglira
Copy link
Copy Markdown
Contributor

@fjglira fjglira commented May 28, 2026

Fix operator image build failure when using Podman as the container runtime. When running inside a Podman VM build container, docker build . fails to transfer the build context to Docker Desktop; the workaround uses a minimal temp directory containing only the Dockerfile and the compiled binary, bypassing the context transfer issue.

The existing Docker path (used in CI) is completely unchanged.

…perator image

While running test locally if you are using purely podman you will get error messages while trying to run the test, adding this podman specific steps will allow any user to run the e2e test or build and push using the script while using podman. The error is because podman uses a VM and seems to be that the chained containers causes errors

Signed-off-by: Francisco Herrera <fjglira@gmail.com>
@fjglira fjglira requested a review from a team as a code owner May 28, 2026 14:40
@codecov
Copy link
Copy Markdown

codecov Bot commented May 28, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.06%. Comparing base (03aa723) to head (1c108e1).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1976      +/-   ##
==========================================
- Coverage   80.14%   80.06%   -0.08%     
==========================================
  Files          51       51              
  Lines        2614     2614              
==========================================
- Hits         2095     2093       -2     
- Misses        395      396       +1     
- Partials      124      125       +1     
Flag Coverage Δ
integration-tests 70.75% <ø> (-0.31%) ⬇️
unit-tests 52.18% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

mkdir -p "${tmp_ctx}/out/linux_${TARGET_ARCH}"
cp "${repo_root}/out/linux_${TARGET_ARCH}/sail-operator" "${tmp_ctx}/out/linux_${TARGET_ARCH}/sail-operator"

docker build \
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be podman build or does it not matter?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ohh, the podman configuration that I have already mount docker in the podman socket and allow to execute docker command but it's running at the end podman. Let me check if the behaviour keeps the same (I don't think there is going to be any change)

@fjglira
Copy link
Copy Markdown
Contributor Author

fjglira commented May 29, 2026

/retest

@istio-testing
Copy link
Copy Markdown
Collaborator

@fjglira: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
e2e-kind-multicluster_sail-operator_main 1c108e1 link true /test e2e-kind-multicluster
Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants