mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-08-08 09:55:42 +00:00
259c79963f
Firstly, reset is now managed by the runtime itself as a part of initialization. This ensures that it can be used even with runtimes that would otherwise fail to be created - most notably, when the user has changed a core path (runroot/root/tmpdir/staticdir). Secondly, we now attempt a best-effort removal even if the store completely fails to be configured. Third, we now hold the alive lock for the entire reset operation. This ensures that no other Podman process can start while we are running a system reset, and removes any possibility of a race where a user tries to create containers or pull images while we are trying to perform a reset. [NO NEW TESTS NEEDED] we do not test reset last I checked. Fixes #9075 Signed-off-by: Matthew Heon <mheon@redhat.com> |
||
|---|---|---|
| .. | ||
| parse | ||
| terminal | ||
| archive.go | ||
| auto-update.go | ||
| containers.go | ||
| containers_runlabel.go | ||
| containers_runlabel_test.go | ||
| containers_stat.go | ||
| events.go | ||
| generate.go | ||
| healthcheck.go | ||
| images.go | ||
| images_list.go | ||
| images_test.go | ||
| manifest.go | ||
| network.go | ||
| play.go | ||
| play_test.go | ||
| pods.go | ||
| pods_stats.go | ||
| runtime.go | ||
| secrets.go | ||
| system.go | ||
| trust.go | ||
| volumes.go | ||