Valentin Rothberg 4e29ce2baf use cached containers.conf ... Use `Default()` instead of re-loading containers.conf. Also rework how the containers.conf objects are handled for parsing the CLI. Previously, we were conflating "loading the defaults" with "storing values from the CLI" with "libpod may further change fields" which ultimately led to various bugs and test failues. To address the issue, separate the defaults from the values from the CLI and properly name the fields to make the semantics less ambiguous. [NO NEW TESTS NEEDED] as it's not a functional change. Fixes: containers/common/issues/1200 Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>		2022-10-21 14:03:14 +02:00
..
completion.go	health check: add on-failure actions	2022-09-09 13:02:05 +02:00
completion_test.go	bump golangci-lint to v1.49.0	2022-10-17 09:19:41 +02:00
create.go	use cached containers.conf	2022-10-21 14:03:14 +02:00
create_opts.go	use cached containers.conf	2022-10-21 14:03:14 +02:00
create_test.go	linter: enable unconvert linter	2022-05-19 13:59:15 +02:00
default.go	Support setting image_volume_mode in containers.conf	2022-05-26 14:16:26 -04:00
diffChanges.go	cmd/podman: switch to golang native error wrapping	2022-06-30 12:58:57 +02:00
inspect.go	fix podman pod inspect to support multiple pods	2022-09-08 10:28:42 +02:00
netflags.go	use cached containers.conf	2022-10-21 14:03:14 +02:00
sign.go	podman ssh work, using new c/common interface	2022-08-09 14:00:58 -04:00