Hi everyone,
Thank you for you patience here. During the investigation it seemed that the error was caused by the issue in Podman and according to release notes was fixed in version 4.8.1. Upgrading to that version on our end has fixed the issue.
Please try it out and let us know how it goes.
Thanks,
Jakub