(Marking invalid as lxc on lucid is officially unsupported, and network
namespaces are not supported in the kernel :( )
** Changed in: lxc (Ubuntu Lucid)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
(Marking invalid as lxc on lucid is officially unsupported, and network
namespaces are not supported in the kernel :( )
** Changed in: lxc (Ubuntu Lucid)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Nigel - thanks, but near as I can tell all that was done on August 30. Likely
I goofed up and
missed some step. Should I have placed *this* bug in FixReleased state? (I
thought that was
about the development release version, which is N/A here)
Thanks for any hints.
** Description changed:
** Branch linked: lp:~serge-hallyn/ubuntu/lucid/lxc/fix-separate-var
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not start
https://bugs.launchpad.net/bugs/566827
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, I am closing it because the bug has been fixed
in the latest development version of Ubuntu - Maverick Meerkat.
** Also affects: lxc (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed
Thanks for the swift reply Serge. Sadly I've never applied a patch, at
least not without instruction. How exactly is the patch applied? Should
I apply it to the .deb from the repos or the attached amd64 .deb?
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
Patch applied using Ubuntu wiki and forum how to's. Installs ok. Testing
for the bug now. Any feedback for a noob packager would be appreciated!
** Attachment added: amd64 deb #2 of proposed fix
Do not use the 'amd64 deb of proposed fix' (#27). I was to hasty and
should have known patching/packaging could not be that easy. I left the
attachment in the event someone can tell me what I'm failing to do
properly. I used 'dpkg -i lxc_0.6.5-1_amd64.deb' to install which might
have not been the
Thanks Rich - I went ahead and proposed the fix for merge into lucid-
proposed.
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not start
https://bugs.launchpad.net/bugs/566827
You received this bug notification because you are a member of Ubuntu
Please follow the full list of SRU procedures documented at
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure, specfically,
please provide a debdiff and subscribe sponsors first.
** Changed in: lxc (Ubuntu)
Status: Fix Committed = Confirmed
--
[lucid] 0.6.5 cannot umount /var
Is the patch applied to the amd64 .deb attached in post #13? Or another
case of post #20? :)
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not start
https://bugs.launchpad.net/bugs/566827
You received this bug notification because you are a
Quoting Rich Gray (566...@bugs.launchpad.net):
Is the patch applied to the amd64 .deb attached in post #13? Or another
case of post #20? :)
The amd64 .deb in post #13 was wrong - the patch wasn't being applied.
The one in post 20 was confirmed to fix the bug. The debdiff is in
comment #23 for
** Description changed:
+ IMPACT: users with separate /var partition cannot start containers
+
+ HOW ADDRESSED: the fix was applied upstream some time ago, and is
+ rolled into the maverick package. The proposed package attached to this
+ bug cherrypicks the specific patch.
+
+ PATCH: a
** Attachment added: Debdiff of package fixing this bug
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/566827/+attachment/1530790/+files/debdiff
** Description changed:
+ === SRU request description
+ =
+
IMPACT: users with
Thanks for the package.
The package work correctly but don't fixe the bug :-/
I'm sorry !
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not start
https://bugs.launchpad.net/bugs/566827
You received this bug notification because you are a member
Hugin - that's surprising! Thanks for testing. Back to the original
email thread...
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not start
https://bugs.launchpad.net/bugs/566827
You received this bug notification because you are a member of
** Attachment added: corrected i386 lxc package
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/566827/+attachment/1523039/+files/lxc_0.6.5-1ubuntu3_i386.deb
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not start
Hugin,
that was my complete lack of debian package handling skills at fault -
the patch was not being applied! Please try this latest one that I
just uploaded (lxc_0.6.5-1ubuntu3_i386.deb).
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not
\o/ this package fixe the bug.
Thanks for your work.
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not start
https://bugs.launchpad.net/bugs/566827
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm really interested in testing the package.
Actually the package failed to build.
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not start
https://bugs.launchpad.net/bugs/566827
You received this bug notification because you are a member of
Quoting Hugin (566...@bugs.launchpad.net):
I'm really interested in testing the package.
Actually the package failed to build.
Grr, thanks - I'll fix that up later this morning, build
locallly, and upload to this report.
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate
Locally compiled .deb of the proposed fix.
** Attachment added: lxc_0.6.5-1ubuntu1_amd64.deb
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/566827/+attachment/1520341/+files/lxc_0.6.5-1ubuntu1_amd64.deb
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
Sorry, Hugin, I had failed to include quilt in the new build-depends. I've
re-uploaded with that fixed, and the result should be in my ppa in a few
hours. In the meantime, the locally built version (which succeeded since
quilt was already installed here) is uploaded in comment 13. Please let
me
Sorry, Hugin, I had failed to include
quilt in the new build-depends. I've
re-uploaded with that fixed, and the result should be in my
ppa in a few
hours. In the meantime, the locally built version
(which succeeded since
quilt was already installed here) is uploaded in comment
13.
** Attachment added: i386 deb of proposed fix
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/566827/+attachment/1520904/+files/lxc_0.6.5-1ubuntu2_i386.deb
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not start
Hugin: here is the i386 version.
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not start
https://bugs.launchpad.net/bugs/566827
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This bug affect my system too :
Ubuntu 10.04 LTS
# lxc-version
lxc version: 0.6.5
# lxc-start -n web
lxc-start: Device or resource busy - could not unmount old rootfs
lxc-start: failed to pivot_root to '/opt/lxc/web/rootfs'
My containers is on another device too.
Cordially
--
[lucid] 0.6.5
Thanks, Hugin, for the reminder. I've uploaded a version of 0.6.5
to my private repo at
https://launchpad.net/~serge-hallyn/+archive/lxc-lucid-lazyumount.
It'll likely take a few hours to build, but then you can
sudo add-apt-repository ppa:serge-hallyn/lxc-lucid-lazyumount
sudo apt-get
(if this package is confirmed to fix the bug, I'll try to get an SRU
to get it into lucid-proposed)
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not start
https://bugs.launchpad.net/bugs/566827
You received this bug notification because you are
Yes, the problem is solved in 0.7 branch of lxc.
There's a patch available and OpenSUSE RPM exists that doesn't contain
the problem being discussed: http://www.mail-archive.com/lxc-
us...@lists.sourceforge.net/msg00266.html
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate
This issue apparently is solved in lxc 0.7.1 included in development
version of Ubuntu (Maverick Meerkat) , so please can you check if this
problem is still affecting you in that version? Thanks
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not
Can you confirm whether this is still a problem on lucid?
** Changed in: lxc (Ubuntu)
Importance: Undecided = Medium
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) = Serge Hallyn (serge-hallyn)
** Changed in: lxc (Ubuntu)
Status: Confirmed = Incomplete
--
[lucid] 0.6.5
The package from your repository did not help :(
System: Ubuntu 10.04 LTS
$ sudo lxc-start -n lxc_web -f config -l DEBUG -o $(tty)
lxc-start 1272588706.041 INFO lxc_conf - tty's configured
lxc-start 1272588706.041 DEBUGlxc_start - sigchild handler set
lxc-start
I have packaged the fix for 0.6.5-1 in ppa:~rye/ppa:
0.6.5-1ubuntu1~ppa1~lucid
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not start
https://bugs.launchpad.net/bugs/566827
You received this bug notification because you are a member of Ubuntu
Correction - the URL for ppa is: ppa:rye/ppa
See https://launchpad.net/~rye/+archive/ppa for more info.
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not start
https://bugs.launchpad.net/bugs/566827
You received this bug notification because you
** Attachment added: force-umount-rootfs.patch
http://launchpadlibrarian.net/44837764/force-umount-rootfs.patch
** Changed in: lxc (Ubuntu)
Status: New = Confirmed
--
[lucid] 0.6.5 cannot umount /var properly if it is on a separate partition -
container does not start
36 matches
Mail list logo
