-
Notifications
You must be signed in to change notification settings - Fork 496
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debian-iptables build fails #1907
Comments
This seems like one of those transient failures we hit in the past. I encountered something similar while developing #1909. Unfortunately
is not very helpful. |
Maybe this might help:
I'll give it a try in #1909 |
I tried that and that fixes it. |
Sounds great, if we're happy with #1909 then we should apply this pattern to all other images. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-contributor-experience at kubernetes/community. |
Rotten issues close after 30d of inactivity. Send feedback to sig-contributor-experience at kubernetes/community. |
@fejta-bot: Closing this issue. In response to this:
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/test-infra repository. |
What happened:
make sub-build-s309x failed.
What you expected to happen:
make sub-build-s390x succeeeds.
How to reproduce it (as minimally and precisely as possible):
make sub-build-s390x
Anything else we need to know?:
Docker version:
buildx verions:
Error-log:
Environment:
cat /etc/os-release
): debianuname -a
):The text was updated successfully, but these errors were encountered: