On Thu, 2010-06-24 at 08:55 +0200, Daniel Lezcano wrote:
: - snip
Console output is not defaulting to the current tty, so you have to specify
lxc-start -n fsn -s lxc.console=$(tty)
That will be fixed for 0.7.1, I will release probably tomorrow.
Will that also be including the ro bind mount
Papp Tamás wrote, On 2010. 06. 24. 21:43:
Daniel Lezcano wrote, On 2010. 06. 24. 8:55:
Console output is not defaulting to the current tty, so you have to
specify
lxc-start -n fsn -s lxc.console=$(tty)
That will be fixed for 0.7.1, I will release probably tomorrow.
I've just
Hi All,
Notes:
==
Bug fixes only.
ChangeLog:
==
Ciprian Dorin, Craciun (1):
lxc to apply mount options for bind mounts
Daniel Lezcano (6):
fix sshd template
fix bad free when reading the configuration file
fix default console to /dev/tty
fix
On 06/22/2010 07:25 AM, John Brendler wrote:
lxc fails to make read-only bind mounts as documented. Read-only bind
mounts are important to many use cases.
A simple patch has been submitted to the lxc-devel mailing list (by
Ciprian Dorin), but when I last checked, it was not clear if any
Daniel Lezcano wrote, On 2010. 06. 24. 22:38:
That's probably mean the container is already running. Did you checked
with lxc-ps --name fsn ?
Well, you are right. But shouldn't it also show it with lxc-ps --lxc ?
$ lxc-destroy -n fsn
That will destroy the container, remove the container's
On 06/24/2010 11:16 PM, Papp Tamás wrote:
Daniel Lezcano wrote, On 2010. 06. 24. 22:38:
That's probably mean the container is already running. Did you checked
with lxc-ps --name fsn ?
Well, you are right. But shouldn't it also show it with lxc-ps --lxc ?
Yes, correct. The --lxc option will
