diff options
| author | Bruce Ashfield <bruce.ashfield@windriver.com> | 2016-05-02 13:59:55 -0400 |
|---|---|---|
| committer | Bruce Ashfield <bruce.ashfield@windriver.com> | 2016-05-02 14:02:42 -0400 |
| commit | fd1a6d1bd31ead568f17a24ab7d7487c7f3514d6 (patch) | |
| tree | a8a1f005699d87a98cd08b87818ccf06b0729dba /recipes-devtools/protobuf/files/protobuf-allow-running-python-scripts-from-anywhere.patch | |
| parent | e919b641bbfec86ef328da613a1c47337cb5b26e (diff) | |
| download | meta-virtualization-fd1a6d1bd31ead568f17a24ab7d7487c7f3514d6.tar.gz | |
runc: initial recipe
With the update to docker 1.11.x, we must also introduce runc. From the
runc site:
runC is a CLI tool for spawning and running containers according to the OCP specification.
Containers are started as a child process of runC and can be embedded into various other
systems without having to run a Docker daemon.
runC is built on libcontainer, the same container technology powering millions of
Docker Engine installations.
Docker images can be run with runC.
So not only is runc required for docker, it is useful for any system that wants
to run OCP containers AND docker containers.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Diffstat (limited to 'recipes-devtools/protobuf/files/protobuf-allow-running-python-scripts-from-anywhere.patch')
0 files changed, 0 insertions, 0 deletions