various issues with podman 4.8

[dustymabe]

There are a few issues with podman 4.8 that makes me want to pin it for the upcoming testing and next releases.

• Error: database libpod root directory (staticdir) does not match our libpod root directory (staticdir) containers/podman#20872
  • For this one on FCOS your $HOME env var should always include /var/home, but I think for the silverblue users in the reported issue that wasn't always true or something. Anyway, I can reproduce this issue if I set $HOME to /home/core instead of /var/home/core and run podman and then upgrade to 4.8 so it's probably worth waiting for the fix in 4.8.1.
• https://bugzilla.redhat.com/show_bug.cgi?id=2252000
  • a bunch of complaints on Silverblue about a newuidmap file having the wrong setuid settings
  • I haven't seen this on FCOS, not sure what is triggering it.
• build-arch jobs failing with "Error: unmarshalling error into &errorhandling.ErrorModel" coreos-assembler#3678
  • Unmarshalling error when using podman exec containers/podman#20821
  • If we hit it in COSA other people are bound to hit it in FCOS.

[jlebon]

Probably after the first rounds of issues are fixed, we should let it bake in next first.

[travier]

Might be interesting to prioritize Fedora gating for podman package updates as it's not the first time it breaks on major releases.

[jkonecny12]

Totally agree on that. Given to the increased popularity of ostree based systems the podman package is more and more important for daily workflow for people.