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

[Serge Hallyn]

This has taken me longer than it should have because I made some bad
initial assumptions.

The appearance of a /dev/shm directory was a bit of a false flag.  That
was happening because the chroot case higher in initscripts.postinst was
failing to create the /dev/shm symbolic link in the first place.  It's
source directory (/run/shm) needed to first be created, and then the
arguments to compat_link() were reversed.  I assumed they were correct
because they were the same for the /var/lock symlink which is correctly
created - but in fact the /var/lock symlink exists before that block of
code.

Here is a debdiff which appears to fix the /dev/shm symlink creation in
a container for me.

** Patch added: "sysvinit-shm.debdiff"
   https://bugs.launchpad.net/launchpad/+bug/974584/+attachment/3152926/+files/sysvinit-shm.debdiff

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

Title:
  Semaphores cannot be created in lxc container

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