3 ms·

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

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?

viraptor 3y ago
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 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.
- gigatexal 3y ago
  Cool! I’ll look at it and add it to my post. We use AMIs so might be nice to have written down. Thanks for following up!
  - gigatexal 3y ago
    Can you share what the logs suggest to change the policy to?