TipsAndTricks/BuildingAndRunningClearContainersonTarget: Difference between revisions
(Created page with "== What & Why == Clear containers offer a hybrid solution that encompasses the advantages of hypervisor security and container deployment. So, we wanted to see if they could ...") |
|||
| Line 13: | Line 13: | ||
commit: f92d50ad54003298c139de59777f07588683cdc2 | commit: f92d50ad54003298c139de59777f07588683cdc2 | ||
==== Dependencies you need ==== | ==== Dependencies you need ==== | ||
===== Layers ===== | |||
===== Conf Changes ===== | |||
===== Additional Dependencies to Bitbake ===== | |||
These are the additional recipes I built in addition to the base I outlined above. They could be added all at once in the local.conf, if you want. | |||
bitbake libcheck mdadm psmisc json-glib libmnl ossp-uuid autoconf-archive python-setuptools libcap-ng tunctl | |||
These are additional packages I built for convenience, but they are not required: | |||
bitbake less zile ntp rsync minicom | |||
Once built these can be installed on the board. Note that we need the dev pkgs as we are mostly completing build requirements for pieces of CC. | |||
dnf install tunctl python-dev python-setuptools-dev libcap-ng-dev libcheck-dev libmnl-dev libjson-glib-1.0-dev autoconf-archive-dev libcap-ng-dev python-setuptools-dev | |||
and the convenient ones: | |||
dnf install zile less ntp rsync minicom | |||
===== | |||
=== The Hypervisor === | === The Hypervisor === | ||
Revision as of 15:04, 8 July 2017
What & Why
Clear containers offer a hybrid solution that encompasses the advantages of hypervisor security and container deployment. So, we wanted to see if they could be used in a YP environment. This was done for Clear Containers 2.2 based on YP master around the time of 2.4 RC1/2.
Note: this is a Proof of Concept, done by building on target. The eventual goal would be to create a standard recipe to allow the clear containers to be built in the standard way. Hopefully, this guide will help with that by outlining the parts, dependencies, and configuration steps. This guide assumes you already have docker running on your target by having followed Running Docker on your image . The target example is being done with an Intel Nuc. I have successfully run the same code on a Minnowboard Turbot.
The Pieces
Clear Containers are comprised of a set of software and binaries.
The Runtime
This comes from [clear oci runtime]. While getting it to work, I followed the development model outlined in Leveraging Rpm Package Feeds. Here I will list the dependencies to make it shorter.
Which Clear was this?
cc-oci-runtime version: 2.2.0 spec version: 1.0.0-rc1 commit: f92d50ad54003298c139de59777f07588683cdc2
Dependencies you need
Layers
Conf Changes
Additional Dependencies to Bitbake
These are the additional recipes I built in addition to the base I outlined above. They could be added all at once in the local.conf, if you want.
bitbake libcheck mdadm psmisc json-glib libmnl ossp-uuid autoconf-archive python-setuptools libcap-ng tunctl
These are additional packages I built for convenience, but they are not required:
bitbake less zile ntp rsync minicom
Once built these can be installed on the board. Note that we need the dev pkgs as we are mostly completing build requirements for pieces of CC.
dnf install tunctl python-dev python-setuptools-dev libcap-ng-dev libcheck-dev libmnl-dev libjson-glib-1.0-dev autoconf-archive-dev libcap-ng-dev python-setuptools-dev
and the convenient ones:
dnf install zile less ntp rsync minicom
