3e983806e0
In order to find the container hash, the "/proc/$PID/cgroup" file will return several lines, some of them with the patterns: .*/libpod-<container_ID>.scope .*/libpod-conmon-<container_ID>.scope The search pattern should look for "/libpod-" and the rest of the expression will extract the container ID. That will prevent the issue reported in the related bug, when the "pids:..." line does not contain this information. Change-Id: I0c017d022fbad9a8f99e5f27a7245f84de483950 Closes-Bug: #1990990 |
||
---|---|---|
.. | ||
derive_pci_passthrough_whitelist.py | ||
kill-script | ||
neutron-agents-ib-config-container-puppet.yaml | ||
neutron-api-container-puppet.yaml | ||
neutron-base.yaml | ||
neutron-cleanup | ||
neutron-cleanup.service | ||
neutron-dhcp-container-puppet.yaml | ||
neutron-l3-container-puppet.yaml | ||
neutron-metadata-container-puppet.yaml | ||
neutron-mlnx-agent-container-puppet.yaml | ||
neutron-ovn-dpdk-config-container-puppet.yaml | ||
neutron-ovs-agent-container-puppet.yaml | ||
neutron-ovs-dpdk-agent-container-puppet.yaml | ||
neutron-plugin-ml2-cisco-vts-container-puppet.yaml | ||
neutron-plugin-ml2-container-puppet.yaml | ||
neutron-plugin-ml2-mlnx-sdn-assist-container-puppet.yaml | ||
neutron-plugin-ml2-ovn.yaml | ||
neutron-plugin-ml2.yaml | ||
neutron-sfc-api-container-puppet.yaml | ||
neutron-sriov-agent-container-puppet.yaml |