Thanks for submitting this bug. The problem is due to /run/shm not
existing in the cloud images.
The ubuntu-cloud image fixes the /dev/shm by doing:
if [ ! -L $rootfs/dev/shm ] && [ -d $rootfs/run/shm ] && [ -e
$rootfs/dev/shm ]; then
mv $rootfs/dev/shm $rootfs/dev/shm.bak
ln -s /run/shm $rootfs/dev/shm
fi
The second test fails because $rootfs/run/shm does not exist.
Since /run/shm will be created at runtime, I see no reason not to drop the
second part
of the test. I'll suggest that to the list - there may be reasons I'm not
considering.
** Summary changed:
- Permission denied when creating semaphore in container
+ Permission denied when creating semaphore in ubuntu-cloud container
** Changed in: lxc (Ubuntu)
Importance: Undecided => High
** Changed in: lxc (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353734
Title:
Permission denied when creating semaphore in ubuntu-cloud container
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1353734/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
