Kata Containers CNI Network Problems on kata 3.2
Dear Kata Containers Community, I'm the user of Kata Containers from Haier Corp of China。Now I want your support to resolve my problems. I run Kata(version:3.2.0) containers on Containerd (v1.7.9) with CNI Network, and the hypervisor is ACRN(V3.2.0) 。Now I can run a kata containers on acrn hypervisor,but the SOS cannot communicate with each other over the cni network,but it works when using hypervisor QEMU。 Here are my steps: 1. Create cni conf file cat << EOF | tee /etc/cni/net.d/redisnet.conf { "cniVersion": "0.4.0", "name": "redisnet", "type": "bridge", "bridge": "cni0", "isDefaultGateway": true, "forceAddress": false, "ipMasq": true, "hairpinMode": true, "ipam": { "type": "host-local", "subnet": "10.77.0.0/16" } } EOF 2. Create networkspace and add network into it. ip netns add redisnet export CNI_PATH=/opt/cni/bin cnitool add redisnet /var/run/netns/redisnet cnitool check redisnet /var/run/netns/redisnet [https://ihaier.feishu.cn/space/api/box/stream/download/asynccode/?code=ZWYzY...] I am now able to ping 10.77.0.2. [https://ihaier.feishu.cn/space/api/box/stream/download/asynccode/?code=MGVhM...] 3. Start a kata container with CNI Network ctr run --snapshotter devmapper --runtime "io.containerd.kata.v2" --with-ns=network:/var/run/netns/redisnet -d registry2-qingdao.cosmoplat.com/62_edegecloud/ubuntu-vim-ip:22.04 kata-test sh but the container's eth0 is link down. [https://ihaier.feishu.cn/space/api/box/stream/download/asynccode/?code=YjJiN...] Now I cannot ping 10.77.0.2。 [https://ihaier.feishu.cn/space/api/box/stream/download/asynccode/?code=MmM0M...] could you please help me figure out where is wrong about my steps? If not wrong ,could you please help me resolve this problems? Here are some logs and configs of my test. Thanks and Best Regards, Jason Yang The information transmitted is intended solely for the use of the addressee and may contain confidential and/or privileged material. Any unauthorized disclosure, reproduction, distribution, dissemination, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the email together with any material attached (if any) completely from any device immediately. Unless otherwise stated, any views or opinions expressed in this email are solely those of the author and do not necessarily represent those of Haier Group. 本邮件可能包含敏感信息且仅限于发给指定的收件人,任何未经授权泄露、复制、散布或传播此信息的行为将被禁止。如果您错误收到了此邮件,请及时告知发送者并立即从所有设备中完全删除此邮件及附件。除非另有说明,否则邮件中可能包含的观点或建议仅代表发件者本人,并不代表海尔集团。
Hi Fei Could you open an issue on the kata github https://github.com/kata-containers/kata-containers/issues, and describes the issue and how to reproduce it, so that we can deal with it properly. Thanks. Fupan
2024年3月13日 22:09,Yang Fei 杨斐 <yangfei.cosmo@haier.com> 写道:
Dear Kata Containers Community, I'm the user of Kata Containers from Haier Corp of China。Now I want your support to resolve my problems. I run Kata(version:3.2.0) containers on Containerd (v1.7.9) with CNI Network, and the hypervisor is ACRN(V3.2.0) 。Now I can run a kata containers on acrn hypervisor,but the SOS cannot communicate with each other over the cni network,but it works when using hypervisor QEMU。 Here are my steps: 1. Create cni conf file cat << EOF | tee /etc/cni/net.d/redisnet.conf { "cniVersion": "0.4.0", "name": "redisnet", "type": "bridge", "bridge": "cni0", "isDefaultGateway": true, "forceAddress": false, "ipMasq": true, "hairpinMode": true, "ipam": { "type": "host-local", "subnet": "10.77.0.0/16" } } EOF 2. Create networkspace and add network into it. ip netns add redisnet
export CNI_PATH=/opt/cni/bin cnitool add redisnet /var/run/netns/redisnet cnitool check redisnet /var/run/netns/redisnet <image009.png> I am now able to ping 10.77.0.2.
<image010.png> 3. Start a kata container with CNI Network ctr run --snapshotter devmapper --runtime "io.containerd.kata.v2" --with-ns=network:/var/run/netns/redisnet -d registry2-qingdao.cosmoplat.com/62_edegecloud/ubuntu-vim-ip:22.04 <http://registry2-qingdao.cosmoplat.com/62_edegecloud/ubuntu-vim-ip:22.04> kata-test sh but the container's eth0 is link down. <image011.png> Now I cannot ping 10.77.0.2。 <image012.png>
could you please help me figure out where is wrong about my steps? If not wrong ,could you please help me resolve this problems?
Here are some logs and configs of my test.
Thanks and Best Regards, Jason Yang
The information transmitted is intended solely for the use of the addressee and may contain confidential and/or privileged material. Any unauthorized disclosure, reproduction, distribution, dissemination, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the email together with any material attached (if any) completely from any device immediately. Unless otherwise stated, any views or opinions expressed in this email are solely those of the author and do not necessarily represent those of Haier Group. 本邮件可能包含敏感信息且仅限于发给指定的收件人,任何未经授权泄露、复制、散布或传播此信息的行为将被禁止。如果您错误收到了此邮件,请及时告知发送者并立即从所有设备中完全删除此邮件及附件。除非另有说明,否则邮件中可能包含的观点或建议仅代表发件者本人,并不代表海尔集团。
<persist.json><containerd.log><config(containerd).toml><configuration-acrn.toml><kata-collect-data.log>_______________________________________________ kata-dev mailing list -- kata-dev@lists.katacontainers.io <mailto:kata-dev@lists.katacontainers.io> To unsubscribe send an email to kata-dev-leave@lists.katacontainers.io <mailto:kata-dev-leave@lists.katacontainers.io>
participants (2)
-
fupan li
-
Yang Fei 杨斐