On 2/2/23 15:51, Mark Raynsford via Podman wrote:
inspecting image: size for layer
"13cfed814d5b083572142bc068ae7f890f323258135f0cffe87b04cb62c3742e" is unkno
To me this reads like a podman bug. It should not (in principal) be
possible to kill any `podman XYZ` and have it completely b0RK
container-storage (or anything else persistent).
As a workaround, could you hold of on installing the service until the
system is "fully" booted/updated/settled down? Even by "cheating"
like
with an "at" job or something like that (sorry, I'm not a COS expert)?
---
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
If it ain't broke, your hammer isn't wide 'nough.