[Bug 974584] Re: Semaphores cannot be created in lxc container

[Serge Hallyn]

For P we are working around this in lxc.  No change is needed in P in
initscripts.

For Q and beyond, initscripts should be fixed.  If running from
debootstrap, /dev/shm should be created as a symlink.  That is not
happening.  Note that a system which mounts /dev as devtmpfs (or tmpfs)
will do the right thing on reboot.  But a system which has /dev on
rootfs is stuck with /dev/shm as whatever initscripts' postinst left it
as.

** Also affects: sysvinit (Ubuntu)
   Importance: Undecided
       Status: New

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

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

Title:
  Semaphores cannot be created in lxc container

Status in Launchpad itself:
  Invalid
Status in “lxc” package in Ubuntu:
  Confirmed
Status in “sysvinit” package in Ubuntu:
  Confirmed

Bug description:
  >>> from multiprocessing import synchronize
  >>> synchronize.Lock()
  Traceback (most recent call last):
    File "<stdin>", line 1, in <module>
    File "/usr/lib/python2.6/multiprocessing/synchronize.py", line 117, in __init__
      SemLock.__init__(self, SEMAPHORE, 1, 1)
    File "/usr/lib/python2.6/multiprocessing/synchronize.py", line 49, in __init__
      sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue)
  OSError: [Errno 38] Function not implemented

  Thanks to hallyn, there's a workaround and a fix: adding this line to the container's fstab will fix the problem:
  none dev/shm tmpfs defaults 0 0

  He is updating the ubuntu template with this change.

  Original bug report description was Launchpad related (celery tests
  fail on parallel testing instances)

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/974584/+subscriptions