Confirmed, I still was able to reproduce this on groovy with sudo 1.8.31-1ubuntu1, but groovy is now updated to 1.9.0-1ubuntu1 and now the behavior is correct.
>From the bug report mentioned in comment #3, I found the commit with the corresponding patch. I've added a focal bug task and marked the groovy one fixed. Although it's just a warning, it's pretty noticeable and could cause confusion so I think an SRU may be warranted. ** Patch added: "712afe03195e9747a442cac633b03dc5c8bfa54c.patch" https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1857036/+attachment/5383102/+files/712afe03195e9747a442cac633b03dc5c8bfa54c.patch ** Changed in: sudo (Ubuntu Groovy) Status: Confirmed => Fix Released ** Changed in: sudo (Ubuntu Focal) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857036 Title: `sudo --login --user USERNAME` throws `setrlimit(RLIMIT_CORE): Operation not permitted` error when run inside a container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1857036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
