You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I assume this'd be as simple as including iptables (and any future utils) inside the auto-published buildkit container images. Are there cases where we'd want to exclude them? Currently iptables is added to the integration-tests-base image, so we don't see this issue in CI, assuming this is covered per #4545 (comment). I guess adding iptables (and any other necessary binaries) into cni-plugins-export would be the right place, rather than adding them to buildkit-base.
Brief testing showed this trivial Dockerfile provides a bootstrappable builder:
FROM moby/buildkit:master
RUN apk add --no-cache iptables ip6tables && ln -s /sbin/iptables-legacy /usr/bin/iptables
Attempting to be more selective like cni-plugins-export does was "too hard" because iptables depends on shared libraries, and that seems a bit fragile to me too. (But maybe is justified? Implementor's choice, really.)
The text was updated successfully, but these errors were encountered:
As noted in #4352, the bridge-mode is intended to be default, but simple testing of that case using buildx failed:
I assume this'd be as simple as including iptables (and any future utils) inside the auto-published buildkit container images. Are there cases where we'd want to exclude them? Currently iptables is added to the
integration-tests-base
image, so we don't see this issue in CI, assuming this is covered per #4545 (comment). I guess adding iptables (and any other necessary binaries) into cni-plugins-export would be the right place, rather than adding them to buildkit-base.Brief testing showed this trivial Dockerfile provides a bootstrappable builder:
Attempting to be more selective like cni-plugins-export does was "too hard" because iptables depends on shared libraries, and that seems a bit fragile to me too. (But maybe is justified? Implementor's choice, really.)
The text was updated successfully, but these errors were encountered: