mirror of
https://github.com/containers/podman.git
synced 2026-01-28 16:01:41 -05:00
fe22299f97
When using the docker REST API to wait for a container to be removed, for example, WaitContainerDocker uses a one microsecond interval between poll requests. This ends up being effectively a busy-wait, with the podman system service spinning at > 100% CPU time. The equivalent Podman method uses a 250ms default. Use that for the docker variant, too. I'm going to optimistically assert [NO NEW TESTS NEEDED] - given there's no functional change here, and a test will require some form of mocking or strac'ing the binary for evidence that it's polling less frequently, unless someone who is familiar with podman can briefly explain what kind of test would be appropriate here. Signed-off-by: Peter Edwards <peadar@arista.com> Fixes: #18150