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

juhp · 2020-03-14T04:58:57Z

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?

The text was updated successfully, but these errors were encountered:

millert · 2020-03-14T16:03:55Z

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 · 2020-03-14T17:34:32Z

This is fixed by 712afe0

millert · 2020-03-14T22:27:01Z

Fixed in sudo 1.8.31p1, available now.

juhp · 2020-03-15T04:49:45Z

Thanks so much!!

juhp · 2020-03-21T15:30:40Z

BTW do you plan to add this also to 1.9.0?

millert · 2020-03-21T15:31:42Z

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

juhp · 2020-03-22T13:18:05Z

Great, thank you for confirming

vorburger · 2020-04-04T19:46:06Z

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 · 2020-04-07T15:12:03Z

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 · 2020-04-27T09:47:12Z

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

sudo-project/sudo#42

Newer versions of sudo output this message to stdout when run in a container: sudo: setrlimit(RLIMIT_CORE): Operation not permitted See sudo-project/sudo#42 for details. A simple workaround is to prevent sudo from disabling core dumps. This seems safe enough because if sudo is segfaulting then core files are the least of our worries.

Newer versions of sudo output this message to stderr when run in a container: sudo: setrlimit(RLIMIT_CORE): Operation not permitted See sudo-project/sudo#42 for details. A simple workaround is to prevent sudo from disabling core dumps. This seems safe enough because if sudo is segfaulting then core files are the least of our worries.

This avoids an issue with sudo: sudo-project/sudo#42

This upgrade requires more packages to be upgraded: ffmpeg 4.2.2 chrome 83.0.4103.116 firefox 77.0.1 pip 20.1.1 -> To skip pip warning supervisor 4.2.0 -> To fix failing "ImportError: cannot import name escape' from 'cgi'" change from apt to apt-get -> To remove warning "unstable cli interface" pending next stable release: TODO: upgrade sudo to 1.8.31p1 or 1.9 to fix sudo: setrlimit(RLIMIT_CORE): Operation not permitted sudo-project/sudo#42

ChameleonDevil · 2020-07-16T08:39:34Z

I have just installed sudo inside a Docker container - apt-get update && apt-get install -y sudo and this notification is still in the Docker Ubuntu 20.04 container.

The only thing that work was was this user said above:

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.

Creating a new /etc/sudo.conf file and restarting the container and testing in shell again; those information messages are not showing anymore.

* Avoid issue with sudo package see: sudo-project/sudo#42 Signed-off-by: LanderU <lander.usategui@gmail.com>

Ref: sudo-project/sudo#42 (comment)

* Avoid issue with sudo package see: sudo-project/sudo#42 Signed-off-by: LanderU <lander.usategui@gmail.com>

trying to fix: sudo: setrlimit(RLIMIT_CORE): Operation not permitted --> sudo-project/sudo#42

warpspin · 2020-10-28T13:37:20Z

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.

Raising a hard limit without CAP_SYS_RESOURCE causes EPERM. This is not a bug in the containers in my opinion. The proper solution would probably be that sudo only sets the soft limit to 0 and leaves the hard limit untouched.

This would also solve the even more annoying than the warning problem, where sudo in a rootless container permanently messes up the coredump hard limit for processes it launches without giving any indication it did so.

This helps us reduce time to update dependencies on every CI build since the previous containers used to take about 1 minute. `sudo` had a bug due to which we were not able to create directories. See sudo-project/sudo#42. We used this directories to restore caches. Upgrading the focus dependencies via this commit naturally fixes that bug. Fixes zulip#17854

This helps us reduce time to update dependencies on every CI build since the previous containers used to take about 1 minute. `sudo` had a bug due to which we were not able to create directories. See sudo-project/sudo#42. We used these directories to restore caches. Upgrading the focus dependencies via this commit naturally fixes that bug. Fixes zulip#17854

This helps us reduce time to update dependencies on every CI build since the previous containers used to take about 1 minute. `sudo` had a bug due to which we were not able to create directories. See sudo-project/sudo#42. We used these directories to restore caches. Upgrading the focal dependencies via this commit naturally fixes that bug. Fixes zulip#17854

This helps us reduce time to update dependencies on every CI build since the previous containers used to take about 1 minute. `sudo` had a bug due to which we were not able to create directories. See sudo-project/sudo#42. We used these directories to restore caches. Upgrading the focal dependencies via this commit naturally fixes that bug. Fixes #17854

govindsajgane · 2022-08-10T10:59:48Z

can we make these changes echo "Set disable_coredump false" >> /etc/sudo.conf without rebooting. just to avoid/disturb other people using the same machine?

millert · 2022-08-10T13:14:31Z

Yes, there is no need to reboot. The sudo.conf file is read every time sudo is run.

govindsajgane · 2022-08-10T16:41:33Z

I tried it and it worked. But it worked only once. After that if im trying to change nofile limit using c programm which uses settlimit look like doest work. Setting disable_core false means no core genration? Like core file generation on segmentatiom fault?

govindsajgane · 2022-08-10T16:43:43Z

@millert thank you for your help. Is it correct way to set nofile limit while running process ?? If yes it wont allow without set disble coredump to false.

douglasg14b · 2023-04-23T01:24:18Z

I'm on sudo v 1.9.9 and this still appears to be a problem? I keep being directed to this github thread as the solution to being unable to mount an NFS volume in portainer on a linux container 🤔

This should avoid problems on Linux in cases where sudo does not have CAP_SYS_RESOURCE which may be the case in an unprivileged container. GitHub issue #42

millert closed this as completed Mar 14, 2020

juhp mentioned this issue Mar 21, 2020

sudo gives error in toolbox containers/toolbox#392

Closed

Jean-Baptiste-Lasselle mentioned this issue Mar 23, 2020

SUDO_VERSION_IN_KUBEONE_ALPINE pegasus-io/a-k8s-demo#6

Open

ItsMitchh mentioned this issue Apr 25, 2020

After latest update to support Ubuntu 20.04: setrlimit(RLIMIT_CORE): Operation not permitted AzuraCast/AzuraCast#2740

Closed

vintagesucks added a commit to vintagesucks/caddy-script that referenced this issue Apr 27, 2020

update sudo package

f9a7c69

sudo-project/sudo#42

pietroalbini mentioned this issue May 21, 2020

Blacklist some spurious failures rust-lang/crater#514

Merged

soffokl mentioned this issue Jun 1, 2020

sudo permissions problem in the container. mysteriumnetwork/node#2310

Closed

This was referenced Jun 1, 2020

docs: Use root instead of sudo when interacting with apt gitpod-io/retired-gatsby-website#668

Closed

Workspace creation fails - sudo: setrlimit(RLIMIT_CORE): Operation not permitted gitpod-io/gitpod#1565

Closed

lharzenetter added a commit to lharzenetter/tosca-definitions-workshop that referenced this issue Jun 4, 2020

Use Ubuntu 18.04 instead of latest

19145c9

This avoids an issue with sudo: sudo-project/sudo#42

kstenerud mentioned this issue Jun 8, 2020

connect: connection refused tilt-dev/tilt#3417

Closed

fkorotkov mentioned this issue Jun 25, 2020

Get rid of cirrus user cirruslabs/docker-images-flutter#45

Closed

elcfd mentioned this issue Jul 17, 2020

Ubuntu 20.04 container sudo output warning elcfd/bitbake-docker#8

Closed

amcnicho mentioned this issue Jul 21, 2020

EXTRA_APT_PACKAGES permission errors in notebook image dask/dask-docker#110

Merged

LanderU added a commit to ros2-realtime-demo/pendulum that referenced this issue Aug 5, 2020

Update Dockerfile:

199745d

* Avoid issue with sudo package see: sudo-project/sudo#42 Signed-off-by: LanderU <lander.usategui@gmail.com>

hugojosefson added a commit to hugojosefson/ubuntu-install-scripts that referenced this issue Aug 7, 2020

Remove sudo warning during tests.

e5a17d2

Ref: sudo-project/sudo#42 (comment)

carlossvg pushed a commit to ros2-realtime-demo/pendulum that referenced this issue Aug 15, 2020

Update Dockerfile:

c87e806

* Avoid issue with sudo package see: sudo-project/sudo#42 Signed-off-by: LanderU <lander.usategui@gmail.com>

stanstrup added a commit to rformassspectrometry/metaRbolomics-book that referenced this issue Aug 28, 2020

enable coredump

727f17a

trying to fix: sudo: setrlimit(RLIMIT_CORE): Operation not permitted --> sudo-project/sudo#42

csweichel mentioned this issue Oct 22, 2020

User Namespaced Workspaces gitpod-io/gitpod#2048

Merged

This was referenced Jan 30, 2021

Fix sudo error on node ambientum/ambientum#144

Closed

Fix sudo error on containers ambientum/ambientum#145

Merged

amanagr mentioned this issue Mar 29, 2021

Python caches not saved properly in CI zulip/zulip#17854

Closed

amanagr mentioned this issue Mar 29, 2021

ci: Regenerate bionic and focal containers. zulip/zulip#17858

Merged

Tiryoh mentioned this issue Jul 3, 2022

fix: Update hotfix Tiryoh/docker-ros2-desktop-vnc#50

Merged

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

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

juhp commented Mar 14, 2020 •

edited

millert commented Mar 14, 2020

millert commented Mar 14, 2020

millert commented Mar 14, 2020

juhp commented Mar 15, 2020

juhp commented Mar 21, 2020

millert commented Mar 21, 2020

juhp commented Mar 22, 2020

vorburger commented Apr 4, 2020

juhp commented Apr 7, 2020

uwe72 commented Apr 27, 2020

ChameleonDevil commented Jul 16, 2020

warpspin commented Oct 28, 2020

govindsajgane commented Aug 10, 2022

millert commented Aug 10, 2022

govindsajgane commented Aug 10, 2022

govindsajgane commented Aug 10, 2022

douglasg14b commented Apr 23, 2023

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

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

Comments

juhp commented Mar 14, 2020 • edited

millert commented Mar 14, 2020

millert commented Mar 14, 2020

millert commented Mar 14, 2020

juhp commented Mar 15, 2020

juhp commented Mar 21, 2020

millert commented Mar 21, 2020

juhp commented Mar 22, 2020

vorburger commented Apr 4, 2020

juhp commented Apr 7, 2020

uwe72 commented Apr 27, 2020

ChameleonDevil commented Jul 16, 2020

warpspin commented Oct 28, 2020

govindsajgane commented Aug 10, 2022

millert commented Aug 10, 2022

govindsajgane commented Aug 10, 2022

govindsajgane commented Aug 10, 2022

douglasg14b commented Apr 23, 2023

juhp commented Mar 14, 2020 •

edited