Welcome to Clear Containers 3.0.19 release!
This release includes the Clear Containers support for ARM. Updated the Openshift, Kubernetes and CRI-O versions. A new Makefile target that displays the available arches were introduced. Introduced an architecture framework for ARM.
For more information visit: https://github.com/clearcontainers/runtime/releases/tag/3.0.19
I notice in the boot parameters for the container kernel that iommu=off by
default. What is the reason for this? Won't that prevent virtio devices in
the container VM from using DMA for ring buffer operations? I'm curious if
this is a hard requirement of the CC architecture, or if it is a
performance tweak, or something else entirely? Thanks in advance for any
Welcome to Clear Containers 3.0.17 release!
This release the clear containers image was updated to the latest agent version. The agent include changes to support to online vCPUs and Linux capabilities. Now it has NoNewPrivileges in the api. Finally, the agent now is the subreaper of all processes.
For more information visit: https://github.com/clearcontainers/runtime/releases/tag/3.0.17
Welcome to Clear Containers release 3.0.16!.
For this release we have updated virtcontainers package which provides
important refactoring of the code regarding the proxy and shim
interfaces. Our documentation was updated to remove references to Clear
Containers proxy service (now each VM has its own proxy). The collect-
data script now collects Kata Containers data. Finally, now the kernel
params line options defined in Clear Containers configuration file will
take priority over defaults defined by the runtime.
See the full release notes: