Hi Julio, On Tue, Dec 17, 2019 at 8:09 PM Montes, Julio <julio.montes@intel.com> wrote:
Hi Stefano
I think we'll need a more complex solution [1] (unless someone else has a better patch).
Here [1] you can find a version of kata-runtime that supports all namespaces (yes, including mnt namespace!!) unlike upstream kata-runtime
Since you want to use it for testing net ns, I just enabled it, but if you need other namespace, just uncomment it out from the list [2]
I only tested v1 (no netmom, no vmtemplating) with docker
Thanks for the patches. I tried it, but unfortunately, it doesn't work with the vsock modules with netns support. This is the log, I don't know if can be useful: https://pastebin.com/mG7CfUrV With the old modules (vsock without netns) it works but looking at the netns I'm still seeing only kata-shim and qemu: $ sudo ip netns pids cnitest-1939e49f-19af-3b72-625d-01db153a9fa9 1308 1321 $ ps -p 1308 1321 PID TTY STAT TIME COMMAND 1308 ? Sl 0:05 /usr/bin/qemu-vanilla-system-x86_64 -name sandbox-efd90c46d5b8989886 1321 pts/2 Ssl+ 0:00 /usr/libexec/kata-containers/kata-shim -agent vsock://357155431:1024 This is the log with working kata and vsock modules without netns support: https://pastebin.com/cdHiV5ZV Let me know if I can do other tests or if you want a VM with the vsock modules with netns support. Thanks, Stefano