This repository has been archived by the owner on May 6, 2020. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
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
commandSee issue #95 for more information.
events
commandSee issue #379 for more information.
update
commandSee 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
commandspec
commandMore information Limitations