mirror of https://github.com/containers/podman.git
4b3890ccac
When a user specifies a invalid connection in CONTAINER_CONNECTION then podman should return a proper error saying so. Currently it ignored the error and in rootFlags() just exited early with defining any flags. This caused a panic then when trying to use the flags later. In order to address this first store the connection error in the PodmanConfig struct and not abort right away during flag setup. This is important as the user might have specified a flag with a valid remote connection. As such we check all flags and only when none were given we return the connection error. Also while at it I noticed that the default connection reported via podman --help was wrong as it only used the old containers.conf field for it and did not consider the podman-connections.json default. New regression tests have been added to make sure it behaves correctly. This fixes the problem reported in the PR #22997. Signed-off-by: Paul Holzinger <pholzing@redhat.com> |
||
|---|---|---|
| .. | ||
| reports | ||
| types | ||
| apply.go | ||
| auto-update.go | ||
| container_ps.go | ||
| containers.go | ||
| engine.go | ||
| engine_container.go | ||
| engine_image.go | ||
| events.go | ||
| filters.go | ||
| generate.go | ||
| healthcheck.go | ||
| images.go | ||
| machine.go | ||
| manifest.go | ||
| network.go | ||
| play.go | ||
| pods.go | ||
| secrets.go | ||
| set.go | ||
| system.go | ||
| types.go | ||
| volumes.go | ||