[lxc-users] strange behaviour of grep on lxc-info
Tycho Andersen
tycho.andersen at canonical.com
Mon Sep 8 21:34:16 UTC 2014
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
>
>
>
>
> Does anybody have an idea?:)
I haven't looked into it, but I've seen similar behavior in my LXC
usage.
>
> 10x
> tamas
>
>
> ps.: Is there a nicer way to check the state of container? Something like:
>
> # lxc-info -n t1 --state RUNNING
> STOPPED
[ "$(lxc-info -n t1 -H -s)" = "RUNNING" ]
might be useful.
Tycho
> # echo $?
> 1
> _______________________________________________
> lxc-users mailing list
> lxc-users at lists.linuxcontainers.org
> http://lists.linuxcontainers.org/listinfo/lxc-users
More information about the lxc-users
mailing list