/var/cache.delete /var/cache/*.rpm-ostree install command executes. So if anything in an earlier RPM layer updates the RPM cache, or file timestamps, we'd end up with new layers anyway.ostree compose image, though I'm not sure exactly how that worksdocker://?docker://. But that doesn't seem to be the actual issue anyway, they quoted docs which say it's equivalent.ostree-unverified-image:registry: and ostree-unverified-image:docker://, but discover only currently expects ostree-unverified-registry:, not anything else, so ostree-unverified-image:registry: or ostree-unverified-image:docker:// which should both be equivalent cause it to not work properly./var/cachedelete /var/cache/*rpm-ostree installostree compose imagedocker://docker://ostree-unverified-image:registry:ostree-unverified-image:registry:ostree-unverified-image:docker://ostree-unverified-image:docker://ostree-unverified-registry: