In the past "policy.json" was being installed by this package, but this behavior got changed: https://salsa.debian.org/debian/libpod/commit/3980d63cbc13c51369f3540eb32e53391199b91d Now it's expected to get the policy installed by another recommended package: "buildah". I suppose that such a change was needed to avoid two Debian packages that are compatible trying to manage the same file. Am I right?
But probably some prominent way to tell the user about how to get "policy.json" (and probably also "registries.conf") is needed. If not, people will be frequently stumbling over it. I did and someone else also did: https://github.com/containers/libpod/issues/1742#issuecomment-570952262 I first thought on some message on installation, what might be useful. But in the end probably the place where it's failing is the best place to let the user know about the solution... What about minor patching to report the potential issues? Patching CheckForRegistries@cmd/podman/platform_linux.go [1] would suffice for "registries.conf". I haven't found yet the place where the issue with "policy.json" gets reported... [1] https://github.com/containers/libpod/blob/master/cmd/podman/platform_linux.go#L16
