in container: sudo: setrlimit(RLIMIT_CORE): Operation not permitted

[juhp]

Apparently since version 1.8.29, sudo started outputting this warning in Linux rootless containers:

$ sudo hello > /dev/null
sudo: setrlimit(RLIMIT_CORE): Operation not permitted

which is quite annoying. This is with sudo-1.9.0b1.
(There are quite a lot of reports of this.)

Can something be done to alleviate it?

[millert]

Handling of RLIMIT_CORE appears to be buggy in Linux containers. When sudo tries to restore the original coredump limit (which appears to be RLIM_INFINITY) as uid 0 it gets EPERM, which should not happen. Sudo 1.8.28 just silently ignored the failure, in 1.8.29 and above a warning is written to the standard error. I'll probably just go back to ignoring the failure but this is not actually a bug in sudo.

[millert]

This is fixed by 712afe0

[millert]

Fixed in sudo 1.8.31p1, available now.

[juhp]

Thanks so much!!

[juhp]

BTW do you plan to add this also to 1.9.0?

[millert]

Yes, it was already committed to what will be the 1.9 tree

[juhp]

Great, thank you for confirming

[vorburger]

FTR in the sudo 1.9.x (?) included today in Fedora 30 this wasn't included, yet; but FYI to anyone hitting this, as per https://bugzilla.redhat.com/show_bug.cgi?id=1773148 (and https://ask.fedoraproject.org/t/sudo-setrlimit-rlimit-core-operation-not-permitted/4223) there is a simple workaround:

echo "Set disable_coredump false" >> /etc/sudo.conf

I've used this in https://github.com/vorburger/cloudshell.

[juhp]

FTR in the sudo 1.9.x (?) included today in Fedora 30 this wasn't included, yet

It is fixed in sudo-1.8.31p1-1.fc30 in Fedora update-testing for me - anyway better to report downstream problems to bugzilla. :)

[uwe72]

I am new to linux. sorry to tell, but how can this be possible in a new installed linux, up-to-date