650704c425
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>
|
||
|---|---|---|
| .github | ||
| .travis | ||
| admin | ||
| devel | ||
| fonts/dejavu-fonts-ttf | ||
| ipv6/tayga | ||
| kernel | ||
| lang | ||
| libs | ||
| multimedia | ||
| net | ||
| sound | ||
| utils | ||
| .travis.yml | ||
| .travis_do.sh | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
README.md
OpenWrt packages feed
Description
This is the OpenWrt "packages"-feed containing community-maintained build scripts, options and patches for applications, modules and libraries used within OpenWrt.
Installation of pre-built packages is handled directly by the opkg utility within your running OpenWrt system or by using the OpenWrt SDK on a build system.
Usage
This repository is intended to be layered on-top of an OpenWrt buildroot. If you do not have an OpenWrt buildroot installed, see the documentation at: OpenWrt Buildroot – Installation on the OpenWrt support site.
This feed is enabled by default. To install all its package definitions, run:
./scripts/feeds update packages
./scripts/feeds install -a -p packages
License
See LICENSE file.
Package Guidelines
See CONTRIBUTING.md file.