mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-08-22 00:08:00 +00:00
dce3d6ee9d
Also, do a general cleanup of all the timeout code. Changes include: - Convert from int to *uint where possible. Timeouts cannot be negative, hence the uint change; and a timeout of 0 is valid, so we need a new way to detect that the user set a timeout (hence, pointer). - Change name in the database to avoid conflicts between new data type and old one. This will cause timeouts set with 4.2.0 to be lost, but considering nobody is using the feature at present (and the lack of validation means we could have invalid, negative timeouts in the DB) this feels safe. - Ensure volume plugin timeouts can only be used with volumes created using a plugin. Timeouts on the local driver are nonsensical. - Remove the existing test, as it did not use a volume plugin. Write a new test that does. The actual plumbing of the containers.conf timeout in is one line in volume_api.go; the remainder are the above-described cleanups. Backported to v4.2.0-rhel per RHBZ 2125241 Signed-off-by: Matthew Heon <mheon@redhat.com> |
||
|---|---|---|
| .. | ||
| annotations.go | ||
| checkpoint_restore.go | ||
| config.go | ||
| container.go | ||
| container_inspect.go | ||
| containerstate.go | ||
| diff.go | ||
| errors.go | ||
| exec_codes.go | ||
| fileinfo.go | ||
| healthchecks.go | ||
| info.go | ||
| mount.go | ||
| pod_inspect.go | ||
| podstate.go | ||
| runtime.go | ||
| version.go | ||
| volume_inspect.go | ||