On Mon, Sep 08, 2014 at 11:27:14PM +0200, Tamas Papp wrote:
> 
> hi All,
> 
> # lxc-info -n jay|grep RU
> State:          RUNNING
> State:          RUNNING
> 
> # lxc-info -n jay|grep ve
> Link:           veth2O2K6R
> 
> # lxc-info -n jay|grep jay
> Name:           jay
> Name:           jay
> Name:           jay
> 
> # lxc-info -n jay|grep IP
> IP:             10.0.0.55
> IP:             10.0.0.55
> IP:             10.0.0.55
> IP:             10.0.0.55
> IP:             10.0.0.55
> IP:             10.0.0.55
> IP:             10.0.0.55
> IP:             10.0.0.55
> IP:             10.0.0.55


Interesting bug :)

Note that in most cases you can just query the one field you care about
in a parsable way, e.g. lxc-info -n jay -i -H

> 
> 
> 
> 
> Does anybody have an idea?:)
> 
> 
> 10x
> tamas
> 
> 
> ps.: Is there a nicer way to check the state of container? Something like:
> 
> # lxc-info -n t1 --state RUNNING
> STOPPED
> 
> # echo $?
> 1

lxc-wait -t0 -n t1 -s RUNNING

> _______________________________________________
> lxc-users mailing list
> lxc-users@lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users

-- 
Stéphane Graber
Ubuntu developer
http://www.ubuntu.com

Attachment: signature.asc
Description: Digital signature

_______________________________________________
lxc-users mailing list
lxc-users@lists.linuxcontainers.org
http://lists.linuxcontainers.org/listinfo/lxc-users

Reply via email to