Skip to content
This repository has been archived by the owner on May 6, 2020. It is now read-only.

Release: Clear Containers 3.0.10 #844

Merged
merged 3 commits into from
Dec 6, 2017

Conversation

jcvenegas
Copy link
Contributor

@jcvenegas jcvenegas commented Dec 6, 2017

Release 3.0.10

Welcome to Clear Containers 3.0.10 release!

On this release we have implemented the support to use one proxy instance per VM.
By doing this now each Pod/VM will use an exclusive proxy and the system reliability will increase by removing a single failure point ( using just one proxy for all the pods) .

Added new configurations to configuration.toml to allow to administrator specify how many PCI bridges must be included in the VM, this allow to define how many hot plug devices will be allowed.

Changes

  • hotplug: add default_bridges to configuration file
  • versions: Add missing components
  • proxy: Use one proxy instance per VM

Shortlog

91d5df2 hotplug: add default_bridges to configuration file
41a51c8 versions: Add missing components
725e738 proxy: Use one proxy instance per VM

Compatibility with Docker

Clear Containers 3.0.10 is compatible with Docker v17.09-ce

OCI Runtime Specification

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

Clear Linux Containers image

Clear Containers 3.0.10 requires at least Clear Linux containers image 19490

Clear Linux Containers Kernel

Clear Containers 3.0.10 requires at least Clear Linux Containers kernel v4.9.60-81.container

Installation

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

More information Limitations

@clearcontainersbot
Copy link

kubernetes qa-passed 👍

@jodh-intel
Copy link
Contributor

jodh-intel commented Dec 6, 2017

lgtm

Approved with PullApprove Approved with PullApprove

Update kernel to latest version.

Signed-off-by: Jose Carlos Venegas Munoz <[email protected]>
Changes in package clear-containers-agent:
from b1d92e2aa14d915680e8fe770745a511857ac7ff-17 to
a074983f12ce3c50b8655659bcd81a6c81e4126c-18:

Jose Carlos Venegas Munoz - version bump from
a074983f12ce3c50b8655659bcd81a6c81e4126c-17 to a074983f12ce3c50b8655659bcd81a6c81e4126c-18
Jose Carlos Venegas Munoz - New agent version  a074983

Signed-off-by: Jose Carlos Venegas Munoz <[email protected]>
Changes:

- versions: Add missing components
- proxy: Use one proxy instance per VM

Fixes: clearcontainers#843

Signed-off-by: Jose Carlos Venegas Munoz <[email protected]>
@clearcontainersbot
Copy link

kubernetes qa-failed 👎

@amshinde
Copy link
Contributor

amshinde commented Dec 6, 2017

lgtm.
Now lets wait for the kernel

Approved with PullApprove

@jcvenegas jcvenegas merged commit 3d402d1 into clearcontainers:master Dec 6, 2017
@clearcontainersbot
Copy link

kubernetes qa-failed 👎

mcastelino pushed a commit to mcastelino/runtime that referenced this pull request Dec 6, 2018
reflect.DeepEqual would return false when comparing nil map/slice with
empty map/slice. We would want to return success in such case, since it
is possible for upper layers to send these kind of configs.

Fixes: clearcontainers#844

Signed-off-by: Peng Tao <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants