I'm curious what's different in my environment, but the author doesn't mention any issues with apparmor. On my Ubuntu 22.04 AWS instances the default podman/container policies are broken and prevent you from sending signals. That means "podman stop ..." throws permission issues and you can't "kill contained-pid" either.
(Requires either fixing or disabling the policies)
Author here. But I’m not sure. My environment is just a vanilla Ubuntu setup with my main login user managed by Centrify AD. It’s a bit odd as the user doesn’t exist in /etc/passwd etc.
What is the error you get? Maybe HN can crowdsource a fix. Or is this a known bug?
It's this issue; people ran into it since early 2022. I haven't tracked it down in the Ubuntu issues yet, but basically the same thing fails on today's AMIs. https://github.com/containers/podman/issues/13341
The fix is fairly trivial - if you don't care about apparmor you can disable it. If you do, the usual new policy from the complain log is enough.
I'm on a work issued Ubuntu laptop but I very much live (by choice) in the Redhat ecosystem. I wanted to get Podman on my machine but the AD managed user for my laptop was a pain. So having to run it as a user I didn't login as I ran into issues. Anyway, this blog post is more about me having a place to remember the commands to get it working again in the future but also is a love-letter to Podman and Toolbox.
(Requires either fixing or disabling the policies)