atomic install/pull does not respect registries.insecure #1241
Description
I have found the http: transport in the manpage since writing this bug report, so it's not really all that high priority anymore. I've changed the title, because it would still be nice for atomic to respect registries.insecure, in order to have consistent behavior between all of podman, buildah, atomic, and skopeo WRT HTTP/HTTPS handling.
Original report
I have an image in an insecure local registry, and I'd like to atomic install it in a F28AH VM. Unfortunately, as with podman search, there is no way to configure access to an insecure registry with atomic install and pull. Accessing the registry results in http: server gave HTTP response to HTTPS client.
It would be great if registries.insecure in /etc/containers/registries.conf were honored and/or a --tls-verify flag were added, ideally with the same behavior as in containers/podman#932.