Paul Holzinger a89fef6e2a cleanup: add new --stopped-only option ...

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>

2024-08-27 15:01:23 +02:00

..

createparse.go

Bump Go module to v5

2024-02-08 09:35:39 -05:00

ports_test.go

Unit tests for pkg/specgenutil pkg/signal

2022-04-25 14:48:39 -05:00

ports.go

pkg: switch to golang native error wrapping

2022-07-08 08:54:47 +02:00

specgen.go

specgenutil: record the pod userns in the annotations

2024-07-24 12:10:48 +02:00

specgenutil_test.go

specgenutil: record the pod userns in the annotations

2024-07-24 12:10:48 +02:00

util_test.go

Unit tests for pkg/specgenutil pkg/signal

2022-04-25 14:48:39 -05:00

util.go

cleanup: add new --stopped-only option

2024-08-27 15:01:23 +02:00

volumes_test.go

Replace strings.SplitN with strings.Cut

2024-01-11 13:50:15 +00:00

volumes.go

Add support for image volume subpaths

2024-04-25 14:12:27 -04:00