[Bug 1300927] Re: lxc. procps can not be installed

[Serge Hallyn]

Thanks for the info.  I was mis-remembering and thought we had
changed the procps job to ignore eperm failures, but in fact it
only ignores failures due to unknown keys.

A container is in fact not allowed to change any sysctl values
other than /proc/sys/kernel/shm*.

We could make sysctl ignore the write failures, but that may not
be the safest thing to do long-term.

In the meantime, in your container you should edit /etc/sysctl.conf
and /etc/sysctl.d/* and remove the net.core.somaxconn, fs.suid_dumpable,
kernel.yama.ptrace_scope, kernel.core_uses_pid, kernel.printk, and
kernel,ptr_restrict entries.


** Changed in: procps (Ubuntu)
       Status: New => Confirmed

** Changed in: procps (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1300927

Title:
  lxc. procps can not be installed

Status in “procps” package in Ubuntu:
  Confirmed

Bug description:
  ubuntu 12.04, host kernel - linux-image-3.11.0-18-generic

  lxc

  apt-get upgrade procps (inside lxc)

  Setting up procps (1:3.2.8-11ubuntu6.3) ...
  start: Job failed to start
  invoke-rc.d: initscript procps, action "start" failed.
  dpkg: error processing procps (--configure):
   subprocess installed post-installation script returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1300927/+subscriptions