github/kata-containers
1
0
Fork 2
mirror of https://github.com/kata-containers/kata-containers.git synced 2025-09-05 02:40:18 +00:00
Code Issues Projects Releases Wiki Activity

runtime: Remove docker comments for kata 2.0 configuration.tomls

Browse Source 
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 

Signed-off-by: Gabriela Cervantes <gabriela.cervantes.tellez@intel.com>
This commit is contained in:
Gabriela Cervantes
2022-01-06 16:08:10 +00:00
parent 66510b977d
commit ad16d75c07
4 changed files with 0 additions and 4 deletions

1
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 # `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 # with `internetworking_model=none`. The tap device will be in the host network namespace and can connect to a bridge
# (like OVS) directly. # (like OVS) directly.
# If you are using docker, `disable_new_netns` only works with `docker run --net=none`
# (default: false) # (default: false)
#disable_new_netns = true #disable_new_netns = true

1
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 # `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 # with `internetworking_model=none`. The tap device will be in the host network namespace and can connect to a bridge
# (like OVS) directly. # (like OVS) directly.
# If you are using docker, `disable_new_netns` only works with `docker run --net=none`
# (default: false) # (default: false)
#disable_new_netns = true #disable_new_netns = true

1
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 # `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 # with `internetworking_model=none`. The tap device will be in the host network namespace and can connect to a bridge
# (like OVS) directly. # (like OVS) directly.
# If you are using docker, `disable_new_netns` only works with `docker run --net=none`
# (default: false) # (default: false)
#disable_new_netns = true #disable_new_netns = true

1
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 # `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 # with `internetworking_model=none`. The tap device will be in the host network namespace and can connect to a bridge
# (like OVS) directly. # (like OVS) directly.
# If you are using docker, `disable_new_netns` only works with `docker run --net=none`
# (default: false) # (default: false)
#disable_new_netns = true #disable_new_netns = true