From ad16d75c07bacfeaa9eceb21249c47f40781ea17 Mon Sep 17 00:00:00 2001 From: Gabriela Cervantes Date: Thu, 6 Jan 2022 16:08:10 +0000 Subject: [PATCH] runtime: Remove docker comments for kata 2.0 configuration.tomls This PR removes the reference of how to use disable_new_netns configuration with docker as for kata 2.0 we are not supporting docker and this information was used for kata 1.x Fixes #3400 Signed-off-by: Gabriela Cervantes --- src/runtime/config/configuration-acrn.toml.in | 1 - src/runtime/config/configuration-clh.toml.in | 1 - src/runtime/config/configuration-fc.toml.in | 1 - src/runtime/config/configuration-qemu.toml.in | 1 - 4 files changed, 4 deletions(-) diff --git a/src/runtime/config/configuration-acrn.toml.in b/src/runtime/config/configuration-acrn.toml.in index dff39c7108..4ef211835b 100644 --- a/src/runtime/config/configuration-acrn.toml.in +++ b/src/runtime/config/configuration-acrn.toml.in @@ -205,7 +205,6 @@ disable_guest_seccomp=@DEFDISABLEGUESTSECCOMP@ # `disable_new_netns` conflicts with `internetworking_model=bridged` and `internetworking_model=macvtap`. It works only # with `internetworking_model=none`. The tap device will be in the host network namespace and can connect to a bridge # (like OVS) directly. -# If you are using docker, `disable_new_netns` only works with `docker run --net=none` # (default: false) #disable_new_netns = true diff --git a/src/runtime/config/configuration-clh.toml.in b/src/runtime/config/configuration-clh.toml.in index 4cacb0fad3..8bb8f33419 100644 --- a/src/runtime/config/configuration-clh.toml.in +++ b/src/runtime/config/configuration-clh.toml.in @@ -227,7 +227,6 @@ disable_guest_seccomp=@DEFDISABLEGUESTSECCOMP@ # `disable_new_netns` conflicts with `internetworking_model=bridged` and `internetworking_model=macvtap`. It works only # with `internetworking_model=none`. The tap device will be in the host network namespace and can connect to a bridge # (like OVS) directly. -# If you are using docker, `disable_new_netns` only works with `docker run --net=none` # (default: false) #disable_new_netns = true diff --git a/src/runtime/config/configuration-fc.toml.in b/src/runtime/config/configuration-fc.toml.in index 76060c9bd4..33be336d74 100644 --- a/src/runtime/config/configuration-fc.toml.in +++ b/src/runtime/config/configuration-fc.toml.in @@ -333,7 +333,6 @@ disable_guest_seccomp=@DEFDISABLEGUESTSECCOMP@ # `disable_new_netns` conflicts with `internetworking_model=tcfilter` and `internetworking_model=macvtap`. It works only # with `internetworking_model=none`. The tap device will be in the host network namespace and can connect to a bridge # (like OVS) directly. -# If you are using docker, `disable_new_netns` only works with `docker run --net=none` # (default: false) #disable_new_netns = true diff --git a/src/runtime/config/configuration-qemu.toml.in b/src/runtime/config/configuration-qemu.toml.in index 406c51e75c..fa549731df 100644 --- a/src/runtime/config/configuration-qemu.toml.in +++ b/src/runtime/config/configuration-qemu.toml.in @@ -509,7 +509,6 @@ disable_guest_seccomp=@DEFDISABLEGUESTSECCOMP@ # `disable_new_netns` conflicts with `internetworking_model=tcfilter` and `internetworking_model=macvtap`. It works only # with `internetworking_model=none`. The tap device will be in the host network namespace and can connect to a bridge # (like OVS) directly. -# If you are using docker, `disable_new_netns` only works with `docker run --net=none` # (default: false) #disable_new_netns = true