-
Notifications
You must be signed in to change notification settings - Fork 229
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
iptables-nft not supported in qemu-aarch64-static #191
Comments
Same issue with RPM-based containers. For example, fedora:36 docker image running on:
|
You can't use IpTable in qemu if you use a different architecture than the one from the host. |
@zandercodes Thanks for your reply. Does qemu-aarch64-static plan to support it? |
You can try root@ZanderCodes ~ # docker run --rm --cap-add=NET_ADMIN --cap-add=NET_RAW -it arm64v8/alpine:3.17.3 sh
WARNING: The requested image's platform (linux/arm64/v8) does not match the detected host platform (linux/amd64/v3) and no specific platform was requested
/ # apk add iptables
fetch https://dl-cdn.alpinelinux.org/alpine/v3.17/main/aarch64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.17/community/aarch64/APKINDEX.tar.gz
(1/3) Installing libmnl (1.0.5-r0)
(2/3) Installing libnftnl (1.2.4-r0)
(3/3) Installing iptables (1.8.8-r2)
Executing busybox-1.35.0-r29.trigger
OK: 15 MiB in 18 packages
/ # /sbin/iptables-nft -v
iptables: Failed to initialize nft: Protocol not supported
/ # /sbin/iptables -v
iptables v1.8.8 (legacy): no command specified
Try `iptables -h' or 'iptables --help' for more information.
/ # With emulation not working.
|
@zandercodes Actually, we wants your first case to work. So we cannot rely on qemu-aarch64-static to run arm64 alpine container on amd64 host, right? I mean qemu-aarch64-static cannot simulate iptables inside arm64 container on the amd64 host. |
Same here on M1 mac with toolbox running x86 container on qemu-user-static-x86
Surprisingly everything works fine with rosetta. |
When using nftables based iptables it fails on arm64 because of multiarch/qemu-user-static#191 Signed-off-by: Charly Molter <charly.molter@konghq.com>
When using nftables based iptables it fails on arm64 because of multiarch/qemu-user-static#191 Signed-off-by: Charly Molter <charly.molter@konghq.com>
We cannot currently test _any_ ARM64 platforms under qemu because qemu cannot currently support iptables. See multiarch/qemu-user-static#191 for more details.
We cannot currently test _any_ ARM64 platforms under qemu because qemu cannot currently support iptables. See multiarch/qemu-user-static#191 for more details.
We cannot currently test _any_ ARM64 platforms under qemu because qemu cannot currently support iptables. See multiarch/qemu-user-static#191 for more details. This is because this role actually starts the Docker service before pre-downloading some Docker images, and starting the Docker service requires some interaction with iptables.
Is this a bug report, feature (enhancement) request or question? (leave only one on its own line)
/kind enhancement
Description:
Running cmd iptables-nft shows "nft: Protocol not supported" in the container using arm64 alpine with qemu-aarch64-static.
Steps to reproduce the issue:
using CentOS Linux release 7.8.2003 (Core)
docker run --rm --privileged multiarch/qemu-user-static --reset
docker run --rm -it -v "/usr/bin/qemu-aarch64-static:/usr/bin/qemu-aarch64-static" alpine:3.17.3 sh
apk add iptables
/sbin/iptables-nft --version
Describe the results you received:
/ # /sbin/iptables-nft --version
iptables: Failed to initialize nft: Protocol not supported
Describe the results you expected:
Should be the same output as alpine linux/amd64.
/ # iptables-nft --version
iptables v1.8.8 (nf_tables)
Environment:
CentOS Linux release 7.8.2003 (Core)
Output of
docker version
The text was updated successfully, but these errors were encountered: