This bug was fixed in the package lxc - 0.7.5-3ubuntu62
---
lxc (0.7.5-3ubuntu62) precise-proposed; urgency=low
* lxc.postrm: support purge command (LP: #1029716)
-- Serge Hallyn serge.hal...@ubuntu.com Fri, 27 Jul 2012 03:31:39 +
** Changed in: lxc (Ubuntu Precise)
This bug was fixed in the package sysvinit - 2.88dsf-13.10ubuntu11.1
---
sysvinit (2.88dsf-13.10ubuntu11.1) precise-proposed; urgency=low
* Cherry-pick fix from git to better handle chroot in postinst and change
the check to allow for the case where /dev isn't a mountpoint but
This bug was fixed in the package lxc - 0.7.5-3ubuntu62
---
lxc (0.7.5-3ubuntu62) precise-proposed; urgency=low
* lxc.postrm: support purge command (LP: #1029716)
-- Serge Hallyn serge.hal...@ubuntu.com Fri, 27 Jul 2012 03:31:39 +
** Changed in: lxc (Ubuntu Precise)
This bug was fixed in the package sysvinit - 2.88dsf-13.10ubuntu11.1
---
sysvinit (2.88dsf-13.10ubuntu11.1) precise-proposed; urgency=low
* Cherry-pick fix from git to better handle chroot in postinst and change
the check to allow for the case where /dev isn't a mountpoint but
As discussed in #ubuntu-release, a new lxc package was accepted
resetting the testing period to 0 today.
As both sysvinit and lxc absolutely NEED to land at the same time for
this bug to get fixed without causing any regression, I'd appreciate if
whoever copies sysvinit copies lxc as well,
As discussed in #ubuntu-release, a new lxc package was accepted
resetting the testing period to 0 today.
As both sysvinit and lxc absolutely NEED to land at the same time for
this bug to get fixed without causing any regression, I'd appreciate if
whoever copies sysvinit copies lxc as well,
Tested before/after for both lxc and sysvinit on precise with precise
and quantal containers, everything seems to work as expected.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Tested before/after for both lxc and sysvinit on precise with precise
and quantal containers, everything seems to work as expected.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: lxc (Ubuntu Precise)
Importance: Undecided = High
** Changed in: lxc (Ubuntu Precise)
Status: Fix Released = Triaged
** Changed in: lxc (Ubuntu Precise)
Assignee: (unassigned) = Stéphane Graber (stgraber)
** Changed in: lxc (Ubuntu Quantal)
Assignee: Serge
SRU team: Please wait for matching lxc upload before accepting into
-proposed or moving to -updates or creating container will fail because
of the broken check in lxc-ubuntu and lxc-ubuntu-cloud.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Description changed:
[rational]
Current initscripts doesn't deal properly with chroots, bind-mounting
/run/shm to /dev/shm instead of making the later a symlink to the former.
LXC has been carrying a workaround for that, sadly the workaround stopped
working late in the 12.04 cycle,
Hello Gary, or anyone else affected,
Accepted sysvinit into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/sysvinit/2.88dsf-13.10ubuntu11.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/precise-proposed/lxc
--
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
** Branch linked: lp:ubuntu/precise-proposed/sysvinit
--
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
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu21
---
lxc (0.8.0~rc1-4ubuntu21) quantal; urgency=low
[ Stéphane Graber ]
* Fix lxc-ubuntu and lxc-ubuntu-cloud to fix the /dev/shm workaround to only
trigger when /dev/shm is not a symlink. (LP: #974584)
[ Serge
** Changed in: lxc (Ubuntu Precise)
Importance: Undecided = High
** Changed in: lxc (Ubuntu Precise)
Status: Fix Released = Triaged
** Changed in: lxc (Ubuntu Precise)
Assignee: (unassigned) = Stéphane Graber (stgraber)
** Changed in: lxc (Ubuntu Quantal)
Assignee: Serge
SRU team: Please wait for matching lxc upload before accepting into
-proposed or moving to -updates or creating container will fail because
of the broken check in lxc-ubuntu and lxc-ubuntu-cloud.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Description changed:
[rational]
Current initscripts doesn't deal properly with chroots, bind-mounting
/run/shm to /dev/shm instead of making the later a symlink to the former.
LXC has been carrying a workaround for that, sadly the workaround stopped
working late in the 12.04 cycle,
Hello Gary, or anyone else affected,
Accepted sysvinit into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/sysvinit/2.88dsf-13.10ubuntu11.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/precise-proposed/lxc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974584
Title:
Semaphores cannot be created in lxc container
To manage notifications about this bug go
** Branch linked: lp:ubuntu/precise-proposed/sysvinit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974584
Title:
Semaphores cannot be created in lxc container
To manage notifications about this
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu21
---
lxc (0.8.0~rc1-4ubuntu21) quantal; urgency=low
[ Stéphane Graber ]
* Fix lxc-ubuntu and lxc-ubuntu-cloud to fix the /dev/shm workaround to only
trigger when /dev/shm is not a symlink. (LP: #974584)
[ Serge
This bug was fixed in the package sysvinit - 2.88dsf-13.10ubuntu12
---
sysvinit (2.88dsf-13.10ubuntu12) quantal; urgency=low
* Cherry-pick fix from git to better handle chroot in postinst and change
the check to allow for the case where /dev isn't a mountpoint but /dev/shm
** Description changed:
+ [rational]
+ Current initscripts doesn't deal properly with chroots, bind-mounting
/run/shm to /dev/shm instead of making the later a symlink to the former.
+ LXC has been carrying a workaround for that, sadly the workaround stopped
working late in the 12.04 cycle,
This bug was fixed in the package sysvinit - 2.88dsf-13.10ubuntu12
---
sysvinit (2.88dsf-13.10ubuntu12) quantal; urgency=low
* Cherry-pick fix from git to better handle chroot in postinst and change
the check to allow for the case where /dev isn't a mountpoint but /dev/shm
** Description changed:
+ [rational]
+ Current initscripts doesn't deal properly with chroots, bind-mounting
/run/shm to /dev/shm instead of making the later a symlink to the former.
+ LXC has been carrying a workaround for that, sadly the workaround stopped
working late in the 12.04 cycle,
** Changed in: sysvinit (Ubuntu Quantal)
Assignee: Canonical Foundations Team (canonical-foundations) = Stéphane
Graber (stgraber)
** Changed in: sysvinit (Ubuntu Precise)
Assignee: Canonical Foundations Team (canonical-foundations) = Stéphane
Graber (stgraber)
--
You received this
** Changed in: sysvinit (Ubuntu Quantal)
Assignee: Canonical Foundations Team (canonical-foundations) = Stéphane
Graber (stgraber)
** Changed in: sysvinit (Ubuntu Precise)
Assignee: Canonical Foundations Team (canonical-foundations) = Stéphane
Graber (stgraber)
--
You received this
** Changed in: sysvinit (Ubuntu Precise)
Assignee: (unassigned) = Canonical Foundations Team
(canonical-foundations)
** Changed in: sysvinit (Ubuntu Quantal)
Assignee: (unassigned) = Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you
** Changed in: sysvinit (Ubuntu Precise)
Assignee: (unassigned) = Canonical Foundations Team
(canonical-foundations)
** Changed in: sysvinit (Ubuntu Quantal)
Assignee: (unassigned) = Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you
As this bug is fixed in debian, should the patch be cherrypicked into
ubuntu, or should i open a bug requesting al merge of 2.88dsf-28?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
As this bug is fixed in debian, should the patch be cherrypicked into
ubuntu, or should i open a bug requesting al merge of 2.88dsf-28?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974584
Title:
** Changed in: sysvinit (Debian)
Status: New = Fix Released
--
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
** Branch linked: lp:debian/sysvinit
--
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
** Changed in: sysvinit (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974584
Title:
Semaphores cannot be created in lxc container
To manage notifications
** Branch linked: lp:debian/sysvinit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974584
Title:
Semaphores cannot be created in lxc container
To manage notifications about this bug go to:
I think there are the following possible valid end states that we want
to get to at the end of the postinst:
- we're not in a chroot. /dev/shm is bind mounted to /run/shm, with the
reboot script handling the fix-up to make /dev/shm a symlink to /run/shm before
next boot.
- we're in a chroot
If it does make sense, the implementation that follows is:
if mountpoint -q /dev mountpoint -q /dev/shm; then
compat_link /dev/shm /run/shm
else
[ -d /run/shm ] || mkdir -p /run/shm
mountpoint -q /dev/ || compat_link /run/shm /dev/shm
fi
BTW, I realize there's another possible scenario,
Comment #20 looks very much correct.
The shm_overview(7) man page does say that it always uses a tmpfs
filesystem, so does that mean that there is no way for /dev/shm to be a
unmounted-over directory holding valuable shm state?
In any case, both your code in comment #21 and the update you
I think there are the following possible valid end states that we want
to get to at the end of the postinst:
- we're not in a chroot. /dev/shm is bind mounted to /run/shm, with the
reboot script handling the fix-up to make /dev/shm a symlink to /run/shm before
next boot.
- we're in a chroot
If it does make sense, the implementation that follows is:
if mountpoint -q /dev mountpoint -q /dev/shm; then
compat_link /dev/shm /run/shm
else
[ -d /run/shm ] || mkdir -p /run/shm
mountpoint -q /dev/ || compat_link /run/shm /dev/shm
fi
BTW, I realize there's another possible scenario,
Comment #20 looks very much correct.
The shm_overview(7) man page does say that it always uses a tmpfs
filesystem, so does that mean that there is no way for /dev/shm to be a
unmounted-over directory holding valuable shm state?
In any case, both your code in comment #21 and the update you
** Tags added: rls-q-incoming
--
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:
** Tags added: rls-q-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974584
Title:
Semaphores cannot be created in lxc container
To manage notifications about this bug go to:
** Changed in: lxc (Ubuntu Quantal)
Milestone: ubuntu-12.04 = quantal-alpha-2
--
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
** Changed in: lxc (Ubuntu Quantal)
Milestone: ubuntu-12.04 = quantal-alpha-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974584
Title:
Semaphores cannot be created in lxc container
To
From the debian bug, here is my new suggestion for a replacement for the
ischroot case in initscripts.postinst:
=
if ischroot; then
# Symlink /var/run from /run
# Note var/run is relative
if compat_link /var/run /run; then
#
Here is version tested and working in debootstrap.
diff -u sysvinit-2.88dsf/debian/changelog sysvinit-2.88dsf/debian/changelog
--- sysvinit-2.88dsf/debian/changelog
+++ sysvinit-2.88dsf/debian/changelog
@@ -1,3 +1,12 @@
+sysvinit (2.88dsf-13.10ubuntu12) quantal; urgency=low
+
+ *
From the debian bug, here is my new suggestion for a replacement for the
ischroot case in initscripts.postinst:
=
if ischroot; then
# Symlink /var/run from /run
# Note var/run is relative
if compat_link /var/run /run; then
#
Here is version tested and working in debootstrap.
diff -u sysvinit-2.88dsf/debian/changelog sysvinit-2.88dsf/debian/changelog
--- sysvinit-2.88dsf/debian/changelog
+++ sysvinit-2.88dsf/debian/changelog
@@ -1,3 +1,12 @@
+sysvinit (2.88dsf-13.10ubuntu12) quantal; urgency=low
+
+ *
** Bug watch added: Debian Bug tracker #674178
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674178
** Also affects: sysvinit (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674178
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: sysvinit (Debian)
Status: Unknown = New
--
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
** Bug watch added: Debian Bug tracker #674178
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674178
** Also affects: sysvinit (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674178
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: sysvinit (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974584
Title:
Semaphores cannot be created in lxc container
To manage notifications
Doing
debootstrap sid sid
chroot sid dpkg -i /var/cache/apt/archives/initscr*.deb
(on a sid host) also leaves a mount on sid/run/shm.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Doing
debootstrap sid sid
chroot sid dpkg -i /var/cache/apt/archives/initscr*.deb
(on a sid host) also leaves a mount on sid/run/shm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974584
(thinking out loud)
my patch works for a fresh debootstrap. It should have zero effect for
a machine install, since it is only in chroots. Similarly, containers
are treated as hosts so will not be affected when upgraded under lxc.
Cases to still test, then, include an update from oneiric or
My patch is however not right - it somehow leaves /run/shm mounted.
--
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
I wonder if it would be overkill to detect a /dev/shm mount and non-
existent /run/shm and, if both are the case, move the mount. Otherwise,
throw our hands up and assume user did something weird by hand.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Ah, a simple 'chroot dpkg -i *.deb' of course fails because ischroot
fails with /proc not mounted.
Do we care about that? The fix is simple, but if we don't care about it
then I won't add it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
New debdiff which also makes sure proc is mounted before ischroot is
called, so that 'chroot precise-rootfs dpkg -i *.deb' succeeds and does
not leave dangling /run/shm mounts.
** Patch added: sysvinit-shm2.debdiff
The attachment in #15 (sysvinit-shm2.debdiff) is the best fix in my
opinion. I don't have upload rights, and this ought to be reviewed
anyway. If noone speaks up here reviewing the patch in a few days, I'll
ping on irc.
--
You received this bug notification because you are a member of Ubuntu
(thinking out loud)
my patch works for a fresh debootstrap. It should have zero effect for
a machine install, since it is only in chroots. Similarly, containers
are treated as hosts so will not be affected when upgraded under lxc.
Cases to still test, then, include an update from oneiric or
My patch is however not right - it somehow leaves /run/shm mounted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974584
Title:
Semaphores cannot be created in lxc container
To manage
I wonder if it would be overkill to detect a /dev/shm mount and non-
existent /run/shm and, if both are the case, move the mount. Otherwise,
throw our hands up and assume user did something weird by hand.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ah, a simple 'chroot dpkg -i *.deb' of course fails because ischroot
fails with /proc not mounted.
Do we care about that? The fix is simple, but if we don't care about it
then I won't add it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
New debdiff which also makes sure proc is mounted before ischroot is
called, so that 'chroot precise-rootfs dpkg -i *.deb' succeeds and does
not leave dangling /run/shm mounts.
** Patch added: sysvinit-shm2.debdiff
The attachment in #15 (sysvinit-shm2.debdiff) is the best fix in my
opinion. I don't have upload rights, and this ought to be reviewed
anyway. If noone speaks up here reviewing the patch in a few days, I'll
ping on irc.
--
You received this bug notification because you are a member of Ubuntu
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
Per irc discussion with slangasek, further patching is needed to make
sure that the /run/lock and /run-/var/run update works right in an
upgrade with /run transition.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
I can confirm Serge's analysis here. I'm surprised that this hasn't
bitten us more severely before now, given that I see all my compat
symlinks are wrong in my (iteratively upgraded) precise chroots here;
apparently things really don't care so much about the compat these days.
We should
** Tags added: patch
--
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:
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
Per irc discussion with slangasek, further patching is needed to make
sure that the /run/lock and /run-/var/run update works right in an
upgrade with /run transition.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm Serge's analysis here. I'm surprised that this hasn't
bitten us more severely before now, given that I see all my compat
symlinks are wrong in my (iteratively upgraded) precise chroots here;
apparently things really don't care so much about the compat these days.
We should
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974584
Title:
Semaphores cannot be created in lxc container
To manage notifications about this bug go to:
It would appear part of the problem is simply that ischroot, provided by
debianutils, does not work. initscripts' postinst counts on ischroot
working.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
It would appear part of the problem is simply that ischroot, provided by
debianutils, does not work. initscripts' postinst counts on ischroot
working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: sysvinit (Ubuntu)
Importance: Undecided = High
--
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
** Changed in: sysvinit (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974584
Title:
Semaphores cannot be created in lxc container
To manage notifications
Sorry, the workaround I listed above was for precise, and actually was
incomplete (you also need to ln -s /run/shm $rootfs/dev/shm).
For older releases, the /run transition was not done, so /dev/shm is
supposed to be mounted by mountall through /lib/init/fstab. So the
workaround is to add a
Sorry, the workaround I listed above was for precise, and actually was
incomplete (you also need to ln -s /run/shm $rootfs/dev/shm).
For older releases, the /run transition was not done, so /dev/shm is
supposed to be mounted by mountall through /lib/init/fstab. So the
workaround is to add a
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
** Changed in: lxc (Ubuntu)
Milestone: None = ubuntu-12.04
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
--
You received this bug
There are a few parts to this. At core, we need /dev/shm to be a
symbolic link to /dev/shm, which *is* mounted.
/etc/init/mounted-dev.conf is supposed to create that symbolic link.
However, it does not run because we never mount /dev.
If it did run, it would do the wrong thing. That is because
Note, the fix will only affect new containers.
The WORKAROUND for existing containers is to manually rmdir
/var/lib/lxc/{container}/rootfs/dev/shm
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
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
This bug was fixed in the package lxc - 0.7.5-3ubuntu51
---
lxc (0.7.5-3ubuntu51) precise; urgency=low
* 0070-templates-rmdir-dev-shm: in precise containers, rmdir $rootfs/dev/shm
and and create it as a symbolic link to /run/shm. (LP: #974584)
-- Serge Hallyn
** Branch linked: lp:ubuntu/lxc
--
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
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
** Changed in: lxc (Ubuntu)
Milestone: None = ubuntu-12.04
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
--
You received this bug
There are a few parts to this. At core, we need /dev/shm to be a
symbolic link to /dev/shm, which *is* mounted.
/etc/init/mounted-dev.conf is supposed to create that symbolic link.
However, it does not run because we never mount /dev.
If it did run, it would do the wrong thing. That is because
Note, the fix will only affect new containers.
The WORKAROUND for existing containers is to manually rmdir
/var/lib/lxc/{container}/rootfs/dev/shm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974584
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
This bug was fixed in the package lxc - 0.7.5-3ubuntu51
---
lxc (0.7.5-3ubuntu51) precise; urgency=low
* 0070-templates-rmdir-dev-shm: in precise containers, rmdir $rootfs/dev/shm
and and create it as a symbolic link to /run/shm. (LP: #974584)
-- Serge Hallyn
** Branch linked: lp:ubuntu/lxc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/974584
Title:
Semaphores cannot be created in lxc container
To manage notifications about this bug go to:
94 matches
Mail list logo
