clearlinux/clear-linux-documentation
2
0
Fork 0
mirror of https://github.com/clearlinux/clear-linux-documentation.git synced 2026-08-25 09:27:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

bundles/cc: Simplify the Clear Container bundle page

Browse Source 
The CC bundle page had far too much technical detail, and not enough
overview. Simplify the page by removing the tech info and adding some
overview.

Signed-off-by: Graham Whaley <graham.whaley@intel.com>
This commit is contained in:
Graham Whaley
2017-02-28 11:53:23 +00:00
parent 9dede39a6a
commit afdc0162a7
1 changed files with 19 additions and 71 deletions
Download Patch File Download Diff File Expand all files Collapse all files
source/bdl-containers-basic.rst
+19 -71
View File
@@ -3,83 +3,31 @@
containers-basic
################
This bundle provides container applications
Overview
========
Multiple runtime support for Docker
===================================
The `containers-basic` bundle adds the necessary tools to enable running
containers using Docker*. The bundle includes Intel® Clear Containers as an
additional Docker runtime.
Docker\* 1.12+ provides a way to execute containers using different **"oci
runtimes"**. An **"oci runtime"** is software compatible with :abbr:`OCI
(Open Containers Initiative)` specification that is responsible to create
a container.
Clear Containers enables a hardware backed Virtual Machine (VM) based container
runtime, compared with the normal software namespace containers provided by
standard Docker `runc` runtime.
.. note:: Docker in Clear Linux is configured to use 2 runtimes:
Default runtime
===============
If your system has `VT-x` enabled then, under Clear Linux, Clear Containers
will be used as the default Docker runtime, otherwise the standard Docker
`runc` runtime will be used.
**cc-oci-runtime**: This is the default runtime used by docker in Clear Linux (if
Vt-x support is enabled). This runtime provides the capability to create secure
containers using Clear Containers (based VM containers).
**runc**: This runtime is used to spawn and run containers using namespaces and
cgroups (this is the traditional way to create containers used by docker).
To identify which runtimes are available, as well as which is being used as
the default on your installed system, you can run the following command. Clear
Containers runtime will be listed as `cor`::
In Clear Linux, each time a container is created it uses cc-oci-runtime (*A.K.A*
**cor**).
$ sudo docker info | grep Runtime
To start a secure container with cc-oci-runtime aka cor::
For more information on Clear Containers please see the `Clear Containers runtime github`_.
docker run -ti debian sh
In the case you want to start a non secure container. You can
use the option **--runtime=runc** in the docker command **"run"**
To start an non-secure container using runc runtime::
docker run --runtime=runc -ti debian sh
Change default runtime
======================
To modify the default runtime you can override
the stateless docker daemon configuration
creating the file :file:`/etc/systemd/system/docker-cor.service.d/docker.conf`
and adding **--default-runtinme=runc**::
[Service]
ExecStart=/usr/bin/dockerd -H fd:// --storage-driver=overlay --add runtime cor=cc-oci-runtime --default-runtime=runc
HTTP proxy
==========
If you are behind an HTTP proxy server, for example in corporate settings, you
will need to add this configuration in the Docker systemd service file.
First, create a systemd drop-in directory for the docker service::
mkdir /etc/systemd/system/docker-cor.service.d
Now create a file called :file:`/etc/systemd/system/docker-cor.service.d/http-proxy.conf`
that adds the HTTP_PROXY environment variable::
[Service]
Environment="HTTP_PROXY=http://proxy.example.com:80/"
If you have internal Docker registries that you need to contact without proxying
you can specify them via the NO_PROXY environment variable::
Environment="HTTP_PROXY=http://proxy.example.com:80/" "NO_PROXY=localhost,127.0.0.1,docker-registry.somecorporation.com"
Flush changes::
$ sudo systemctl daemon-reload
Verify that the configuration has been loaded::
$ systemctl show --property=Environment docker-cor
Environment=HTTP_PROXY=http://proxy.example.com:80/
Restart Docker::
$ sudo systemctl restart docker-cor
To get more info you can view https://docs.docker.com/engine/admin/systemd/
.. _Clear Containers runtime github: https://github.com/01org/cc-oci-runtime