mirror of https://github.com/containers/podman.git
a89fef6e2a
The podman container cleanup process runs asynchronous and by the time it gets the lock it is possible another podman process already did the cleanup and then did a new init() to start it again. If the cleanup process gets the lock there it will cause very weird things. This can be observed in the remote start API as CI flakes. Fixes #23754 Signed-off-by: Paul Holzinger <pholzing@redhat.com> |
||
|---|---|---|
| .. | ||
| createparse.go | ||
| ports.go | ||
| ports_test.go | ||
| specgen.go | ||
| specgenutil_test.go | ||
| util.go | ||
| util_test.go | ||
| volumes.go | ||
| volumes_test.go | ||