It should be bumped due to the "info" ubus method support.

Signed-off-by: Rafał Miłecki <rafal@milecki.pl>

It allow distinction between not existing and stopped container. So far
querying for not existing container was resulting in:
> ubus call lxc info '{ "name": "foo" }'
{
        "name": "foo",
        "state": "STOPPED",
        "ips": [

        ]
}

Now it's an error and it matches lxc-info command line:

> ubus call lxc info '{ "name": "foo" }'
Command failed: Not found

> lxc-info --name foo
foo doesn't exist

Signed-off-by: Rafał Miłecki <rafal@milecki.pl>

This method allows getting basic info about a queried container. It's
based on the lxc-info command-line tool.

Example output:
> ubus call lxc info '{ "name": "foo" }'
{
        "name": "foo",
        "state": "RUNNING",
        "pid": 2946,
        "ips": [
                "192.168.0.124"
        ]
}

Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Approved-by: Luka Perkov <luka@openwrt.org>

Signed-off-by: Luka Perkov <luka@openwrt.org>

Example call:

$ ubus call lxc create '{ "name": "bar", "template": "download", "args": [ "--no-validate", "--dist", "debian", "--release", "sid", "--arch", "i386" ] }'

Signed-off-by: Luka Perkov <luka@openwrt.org>

Signed-off-by: Luka Perkov <luka@openwrt.org>