Comment # 2 on bug 1222078 from Georg Pfuetzenreuter

Hi,

my issue was that the default storage.conf shipped with the packages did not
work with Podman, causing it to return the reported error. I had to remove
storage.conf and reset Podman. But after the next update, the next non-working
configuration was placed. I understand that if I were to use custom settings,
that I would need to merge them with possible new .rpmnew's during updates as
by design of `noreplace`. But we are not using any custom settings in in this
file, I am fine with the defaults. Hence I figured either a working, or no
configuration should be shipped. Generally if I do not modify the default
configuration, I expect no breakage upon updates.

Hope that clarifies things, otherwise let me know.