You have been subscribed to a public bug:

I fired up a LXD container using ubuntu-daily:f on my machine and every
time I issue a comment inside the container using sudo, I get this
error:

sudo: setrlimit(RLIMIT_CORE): Operation not permitted

I did some digging online and found this was reported against Fedora last fall 
which lead me to this bugzilla report:
https://bugzilla.redhat.com/show_bug.cgi?id=1773148

which seems to tie this to a change in sudo between 1.8.28 and 1.8.29.

Focal has 1.8.31:
bladernr@focal-builder:~/development/kernels-ubuntu/focal$ apt-cache policy sudo
sudo:
  Installed: 1.8.31-1ubuntu1
  Candidate: 1.8.31-1ubuntu1
  Version table:
 *** 1.8.31-1ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
        100 /var/lib/dpkg/status

This is not an issue on Bionic:
bladernr@galactica:~/development/kernels-upstream/mainline$ apt-cache policy 
sudo
sudo:
  Installed: 1.8.21p2-3ubuntu1.2
  Candidate: 1.8.21p2-3ubuntu1.2
  Version table:
 *** 1.8.21p2-3ubuntu1.2 500
        500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
        100 /var/lib/dpkg/status
     1.8.21p2-3ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

>From the redhat bug, the described workaround does clear these messages
up:

# set disable_coredump false

Once I've done that, the error messages go away.

** Affects: sudo (Ubuntu)
     Importance: Undecided
         Status: New

-- 
"sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo 
in 20.04 LXD container
https://bugs.launchpad.net/bugs/1868456
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to sudo in Ubuntu.

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to