Release 2.1.7

Clear Container 2.1.7

• Added shim debug logs when runtime debug option is used #878
• Fixed Kernel panic using swarm #581
• Added Metrics to measure memory running network test #865

Compatibility with Docker

Clear Containers 2.1.7 is compatible with Docker v17.04.0-ce

OCI Runtime Specification

Clear Containers 2.1.7 support the OCI Runtime Specification 1.0.0-rc5

Clear Linux Containers image

Clear Containers 2.1.7 requires at least Clear Linux containers image 14700

Clear Linux Containers Kernel

Clear Containers 2.1.7 requires at least Clear Linux Containers kernel 4.9.24-60

Installation

• Centos
• Ubuntu
• Fedora
• Clear Linux

Issues & limitations

• Qemu segfault (free(): invalid pointer) running dnf install #669
• DNS Resolution in Swarm #854

Release 2.1.6

Clear Container 2.1.6

Fixed issue to run containers with on Centos #850
Fixed failures when running cc-oci-runtime on Ubuntu #837
Added metrics to CPU % consumption for network #843

Compatibility with Docker

Clear Containers 2.1.6 is compatible with Docker v17.04.0-ce

OCI Runtime Specification

Clear Containers 2.1.6 support the OCI Runtime Specification 1.0.0-rc5

Clear Linux Containers image

Clear Containers 2.1.6 requires at least Clear Linux containers image 14700

Clear Linux Containers Kernel

Clear Containers 2.1.6 requires at least Clear Linux Containers kernel 4.9.24-60

Installation

• Centos
• Ubuntu
• Fedora
• Clear Linux

Issues & limitations

• Qemu segfault (free(): invalid pointer) running dnf install #669
• DNS Resolution in Swarm #854

Release 2.1.5

Clear Container 2.1.5

Fixed failure when trying to create a pod #815
Added network test using nginx and ab
Fixed failure obtaining hostname of a replica in Swarm #578
Added installation script for RHEL and CentOS

Compatibility with Docker

Clear Containers 2.1.5 is compatible with Docker v17.04.0-ce

OCI Runtime Specification

Clear Containers 2.1.5 support the OCI Runtime Specification 1.0.0-rc5

Clear Linux Containers image

Clear Containers 2.1.5 requires at least Clear Linux containers image 14700

Installation

• Centos
• Ubuntu
• Fedora
• Clear Linux

Issues & limitations

• Qemu segfault (free(): invalid pointer) running dnf install #669

Release 2.1.4

Security

Fixed cc-proxy socket and parent directory modes

Compatibility with Docker

Clear Containers 2.1.4 is compatible with Docker v17.03.1-ce

Clear Linux Containers image

Clear Containers 2.1.4 requires at least Clear Linux containers image 14590

Installation

• Centos
• Ubuntu
• Fedora
• Clear Linux

Issues & limitations

• OCI spec version 1.0.0-rc5 is still not supported #690
• Qemu segfault (free(): invalid pointer) running dnf install #669
• Swarm support is incomplete: iptables rules aren’t forwarded to the VM. We also have a hard problem to solve with the docker internal DNS proxy listening on a non-routable loopback IP, breaking DNS resolution in Clear Containers #578

Release 2.1.3

Compatibility with docker 17

Fixed compatibility with docker v17.03.1-ce
Added iperf tests to measure network

Installation

• Centos
• Ubuntu
• Fedora
• Clear Linux

Issues & limitations

• OCI spec version 1.0.0-rc5 is still not supported #690
• Qemu segfault (free(): invalid pointer) running dnf install #669
• Swarm support is incomplete: iptables rules aren’t forwarded to the VM. We also have a hard problem to solve with the docker internal DNS proxy listening on a non-routable loopback IP, breaking DNS resolution in Clear Containers #578

Release 2.1.2

Compatibility with CRI-O

Fixed runtime list for pod containers
Added CRI-O integration tests
Fixed intra pod containers volume support
Created cgroups for pods and containers

Documentation

Added fedora installation details
Added RHEL installation details

Issues & limitations

• Clear Containers v2.1.2 is not compatible with docker 1.13.1 #691 #692 #747
• OCI spec version 1.0.0-rc4 is still not supported #690
• Qemu segfault (free(): invalid pointer) running dnf install #669
• Swarm support is incomplete: iptables rules aren’t forwarded to the VM. We also have a hard problem to solve with the docker internal DNS proxy listening on a non-routable loopback IP, breaking DNS resolution in Clear Containers #578

Release 2.1.1

Compatibility with Docker

• Fixed file descriptor leaks #616
• Added MTU support for network interface

Documentation

• Added Clear Containers architecture
• Added Installation instructions for Centos 7
• Added Installation instructions for ClearLinux
• Added Installation instructions for Ubuntu
• Added DAX appendix
• Added small history covering Clear Containers v1.0 and v2.0

Issues & limitations

• Clear Containers v2.1.1 is not compatible with docker 1.13.1 #691 #692 #693
• OCI spec version 1.0.0-rc4 is still not supported #690
• Qemu segfault (free(): invalid pointer) running dnf install #669
• Swarm support is incomplete: iptables rules aren’t forwarded to the VM. We also have a hard problem to solve with the docker internal DNS proxy listening on a non-routable loopback IP, breaking DNS resolution in Clear Containers #578

release 2.1.0

New Features in Clear Containers V2.1.0

• Completely re-architected the communication between the host and guest, a prerequisite for many of the features of V2.1.0.
• Added support for docker exec. We can now execute a new process inside an already running container.
• Execution of docker Run now returns the proper exit status (that of the process within the VM) to the caller.
• We now run the container in pid, mount, uts… namespaces inside the VM to isolate the workload from the guest OS.
• stdout and stderr are correctly forwarded from the process inside the VM to the host.
• We introduced the concept of a POD, enabling Kubernetes® to start Clear Containers via the Container Runtime Interface (CRI-O).
• Improvements to networking: a container can now join multiple docker networks as we propagate the full configuration (interfaces, IPs, routes, hostname, ...) to the VM.
• User & group support. We respond to directives from Docker to start the containerized workload with a specific user and group, one of the many layers to limit the container permissions.
• Added signal support. We now forward signals to the container workload inside the VM:
  docker kill works: For instance, we can use SIGHUP to gracefully restart Apache.
• Improved TTY handling. For example, typing ctrl+c is correctly sent to the VM and resizing terminals works!

Issues & Limitations

Here’s a list of important issues that one should be aware of and will be addressed in future point releases:

• Clear Container V2.1.0 was tested with Docker 1.12.1 and is known not to work with Docker 1.13 (issue #692).
• File descriptor leakage in the Docker daemon (issue #616).
• Qemu segfault (free(): invalid pointer) running dnf install (issue #669).
• Swarm support is incomplete: iptables rules aren’t forwarded to the VM, neither are MTUs. We also have a hard problem to solve with the docker internal DNS proxy listening on a non-routable loopback IP, breaking DNS resolution in Clear Containers. (issue #578).

A more comprehensive list of limitations is available in the Wiki.

2.1.0-rc.6

- Added additional groups and user related tests
- Added docker attach functional tests
- Added back popular containers tests
- Added memory consumption tool
- Fixed invalid file descriptor Glib warning
- Fixed removing stale docker instances after docker rm
- Fixed distcheck, functional and unit tests