# Release 3.0.16

[jcvenegas]

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.

Changes

• scripts: Ignore qemu startup message
• scripts: Fix collect script bug URL
• cc-env: Remove "CC" from output.
• vendor: Update vendoring
• docs: remove references to Clear Containers proxy service
• cc-check: Document "unrestricted_guest" requirement
• scripts: Update collect script for Kata
• config: Allow user-specified kernel params to take priority
• usage: Show project URL in help output

Shortlog

0f8b25d scripts: Ignore qemu startup message
ab1a9f1 build: Add bug URL to help output
719f523 scripts: Fix collect script bug URL
1412ff8 cc-env: Remove "CC" from output.
5e7d03c vendor: Update virtcontainers vendoring
f515c21 vendor: Update Gopkg.toml for new prune syntax
ef63d36 vendor: Remove constraints from packages not directly vendored
e65682c docs: remove references to Clear Containers proxy service
93c71c9 cc-check: Document "unrestricted_guest" requirement
7310433 scripts: Update collect script for Kata
feed1be config: Allow user-specified kernel params to take priority
e7de45d usage: Show project URL in help output

Compatibility with Docker

Clear Containers 3.0.16 is compatible with Docker v17.12-ce

OCI Runtime Specification

Clear Containers 3.0.16 support the OCI Runtime Specification v1.0.0-rc5

Clear Linux Containers image

Clear Containers 3.0.16 requires at least Clear Linux containers image 19350

Clear Linux Containers Kernel

Clear Containers 3.0.16 requires at least Clear Linux Containers kernel v4.9.60-84.container

Installation

• BC-Linux

• Centos

• Clear Linux

• Fedora

• SLES

• Ubuntu

• Developers

Issues & limitations

Docker swarm support

See issue #771 for more

Networking

Adding networks dynamically

Resource management

docker run --cpus=

See issue #341 for more information.

docker run --kernel-memory=

See issue #388 for more information.

shm

cgroup constraints

Capabilities

See issue #51 for more information.

sysctl

tmpfs

Other

checkpoint and restore

docker stats

See issue #200 for more information.

runtime commands

ps command

See issue #95 for more information.

events command

See issue #379 for more information.

update command

See issue #380 for more information.

Networking

Support for joining an existing VM network

docker --net=host

docker run --link

Host resource sharing

docker --device

docker -v /dev/...

docker run --privileged

Other

Annotations

runtime commands

init command

spec command

Host rdmsr warnings

More information Limitations

[jodh-intel]

lgtm

[clearcontainersbot]

kubernetes qa-passed 👍

[jcvenegas]

docker pull failed:

19:08:21 Running command '/usr/bin/docker [docker pull fedora]'
19:08:24 command failed error 'exit status 1'
19:08:24 [docker pull fedora]
19:08:24 Timeout: 600 seconds
19:08:24 Exit Code: 1
19:08:24 Stdout: Using default tag: latest
19:08:24 latest: Pulling from library/fedora
19:08:24 a8ee583972c2: Pulling fs layer
19:08:24 
19:08:24 Stderr: error pulling image configuration: Get https://registry-1.docker.io/v2/library/fedora/blobs/sha256:422dc563ca3260ad9ef5c47a1c246f5065d7f177ce51f4dd208efd82967ff182: EOF
19:08:24 
19:08:24 --- FAIL: TestIntegration (20.26s)
19:08:24 	main_test.go:55: failed to pull docker image: fedora
19:08:24 FAIL
19:08:24 

job restarted

[clearcontainersbot]

kubernetes qa-passed 👍

[grahamwhaley]

I'll note, it looks like the metrics CI failed in some odd way - I'll go check that out - no doubt spurious and not related to this PR.

[grahamwhaley]

Just to update on the metrics CI status - this failed due to timeouts trying to connect to the docker hub.