mirror of
https://github.com/kata-containers/kata-containers.git
synced 2025-08-18 07:58:36 +00:00
kata-deploy: Check crio conf before update
kata-deploy inserts 'manage_network_ns_lifecycle' into crio.conf without any prior checks and if there is a previous entry in the file, this becomes a duplicate causing crio service restart issues. This patch addresses that particular scenario. Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
This commit is contained in:
parent
2b382fdfec
commit
059b48bfa2
@ -65,7 +65,10 @@ function configure_crio() {
|
|||||||
runtime_path = "/opt/kata/bin/kata-fc"
|
runtime_path = "/opt/kata/bin/kata-fc"
|
||||||
EOT
|
EOT
|
||||||
|
|
||||||
sed -i 's|\(\[crio\.runtime\]\)|\1\nmanage_network_ns_lifecycle = true|' "$crio_conf_file"
|
# Replace if exists, insert otherwise
|
||||||
|
grep -Fq 'manage_network_ns_lifecycle =' $crio_conf_file \
|
||||||
|
&& sed -i '/manage_network_ns_lifecycle =/c manage_network_ns_lifecycle = true' $crio_conf_file \
|
||||||
|
|| sed -i '/\[crio.runtime\]/a manage_network_ns_lifecycle = true' $crio_conf_file
|
||||||
}
|
}
|
||||||
|
|
||||||
function configure_containerd() {
|
function configure_containerd() {
|
||||||
|
Loading…
Reference in New Issue
Block a user