Lxc-start should warn if a container is already running
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lxc (Ubuntu) |
Fix Released
|
High
|
Serge Hallyn |
Bug Description
beuno@beuno-
lxc-start: failed to create the command service point
lxc-start: failed to add command handler to mainloop
lxc-start: mainloop exited with an error
Debug log: http://
/var/lib/
/var/lib/
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: lxc 0.7.5-3ubuntu29
ProcVersionSign
Uname: Linux 3.2.0-17-
ApportVersion: 1.92-0ubuntu1
Architecture: i386
Date: Wed Feb 22 12:42:04 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: lxc
UpgradeStatus: Upgraded to precise on 2011-12-02 (82 days ago)
Related branches
Changed in lxc (Ubuntu): | |
importance: | Undecided → High |
assignee: | nobody → Serge Hallyn (serge-hallyn) |
Changed in lxc (Ubuntu): | |
status: | New → Triaged |
summary: |
- Container will no longer start under 12.04 + Lxc-start should warn if a container is already running |
This bug was fixed in the package lxc - 0.7.5-3ubuntu30
---------------
lxc (0.7.5-3ubuntu30) precise; urgency=low
[ Serge Hallyn ] if-container- started: If container startup fails because the
* 0048-warn-
container is already running, give an error message to that effect.
(LP: #938765)
[ Stéphane Graber ] template- sudo-and- cleanup: Always make the user part of the
* 0049-ubuntu-
sudo group. This group has been around since at least 10.04 and is more
reliable than the admin group. Still add the user to the admin group
until 12.04 as some tool expect that. (LP: #938752)
Also fix a minor layout issue in the generate LXC config.
-- Stephane Graber <email address hidden> Wed, 22 Feb 2012 12:33:32 -0500