I plan to investigate the proposed solutions in that issue, but it doesn’t seem like people had success.

We resolved that as best we could for v12. It should ideally have improved support for podman rootless, but maybe not?

It does look like Dovecot is configured to run with chroot atm, I don't think we need that, so if you still have problems and look into how to disable it and find that works, let us know and it can probably be added for v13 (probably looking at May or later though..).

If it's not a big change we could try squeeze it into v12. Otherwise it won't be added into edge until we're preparing for a v13 release.

So I tested by creating /dms/config/dovecot/10-rootless.conf with

#disable chroot for dovecot 
service anvil {
  chroot = 
}
service imap-login {
  chroot = 
}
service pop3-login {
  chroot = 
}

and I mapped that to /etc/dovecot/conf.d/10-rootless.conf in the container
-v /dms/config/dovecot/10-rootless.conf:/etc/dovecot/conf.d/10-rootless.conf:Z

restarted the container, and I can login!

My whole system is a VM running Fedora CoreOS. I use podman as a regular non-root user to run the container. I did not need to change selinux rules or add additional permissions to the container in order to disable chroot in dovecot

EDIT: By the way, I tested running podman as root before adding 10-rootless.conf, and I experienced the same issue, so it did not seem to be an issue with running podman as a regular user.

EDIT 2: And turns out the high cpu usage was from the postsrsd restart loop, but I see that's already being addressed!

So I found more information about why the problem only just began happening -- there was an update to podman which removed the default CAP_CHROOT capability, which would explain why the container had worked before.
https://github.com/containers/podman/releases/tag/v4.4.1

Awesome thank you! We'll try squeeze that into v12 then! ❤️

Opened issue: #3174