Paul Holzinger 0dae50f1d3 Do not store the exit command in container config ... There is a problem with creating and storing the exit command when the container was created. It only contains the options the container was created with but NOT the options the container is started with. One example would be a CNI network config. If I start a container once, then change the cni config dir with `--cni-config-dir` ans start it a second time it will start successfully. However the exit command still contains the wrong `--cni-config-dir` because it was not updated. To fix this we do not want to store the exit command at all. Instead we create it every time the conmon process for the container is startet. This guarantees us that the container cleanup process is startet with the correct settings. [NO NEW TESTS NEEDED] Signed-off-by: Paul Holzinger <pholzing@redhat.com>		2021-11-18 20:28:03 +01:00
..
entities	Merge pull request #12281 from vrothberg/fix-12007	2021-11-17 12:02:37 +01:00
filters	Run codespell to fix spelling	2021-08-11 16:41:45 -04:00
infra	Do not store the exit command in container config	2021-11-18 20:28:03 +01:00
utils	Add filtering functionality to http api secrets list	2021-09-03 10:29:31 +02:00