Just tested in raring, it is definately fixed there.
Please file a new bug with full details about your system and how we can
reproduce, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1046117
I'm still seeing this bug in 0.8.0~rc1-4ubuntu39.12.10.1 on top of btrfs
... are you sure it's fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1046117
Title:
btrfs via symlink not working
To m
This bug was fixed in the package lxc - 0.8.0~rc1-4ubuntu33
---
lxc (0.8.0~rc1-4ubuntu33) quantal; urgency=low
[ Serge Hallyn ]
* 0206-lxc-wait-initialize-timeout: initialize timeout to -1 so lxc-wait
will, by default, wait for the container to enter the requested state.
* d
Thanks for submitting this bug. Indeed if lxc.rootfs is a symbolic
link, it is assumed to be a lvm rootfs.
I tink it should be ssafe to rm -rf --one-filesystem $rootfs if it is a
symbolic link but is not a blockdev.
** Changed in: lxc (Ubuntu)
Status: New => Triaged
** Changed in: lxc (U
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1046117
Title:
btrfs via symlink not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1046117/+s
