Docker announced its first release built on runC and containerd.
Docker said its Engine 1.11 demonstrates real progress with the Open Container Initiative (OCI), which was launched last year with a mission to build a vendor-neutral, portable and open specification and runtime for container-based solutions. Docker donated its container format and runtime to the OCI under the Linux Foundation in June of last year.
In December 2015, Docker introduced containerd, a daemon to control runC., which is the first compliant implementation of the Open Containers Runtime specification and the default executor bundled with Docker Engine.
Some highlights of Docker Engine 1.11:
https://blog.docker.com/2016/04/docker-engine-1-11-runc/
Docker said its Engine 1.11 demonstrates real progress with the Open Container Initiative (OCI), which was launched last year with a mission to build a vendor-neutral, portable and open specification and runtime for container-based solutions. Docker donated its container format and runtime to the OCI under the Linux Foundation in June of last year.
In December 2015, Docker introduced containerd, a daemon to control runC., which is the first compliant implementation of the Open Containers Runtime specification and the default executor bundled with Docker Engine.
Some highlights of Docker Engine 1.11:
- DNS round robin load balancing between containers with Docker’s networking.
- VLAN support (experimental)
- IPv6 service discovery: Engine’s DNS-based service discovery system can now return AAAA records.
- Yubikey hardware image signing
- Labels on networks and volumes
- Better handling of low disk space with device mapper storage
https://blog.docker.com/2016/04/docker-engine-1-11-runc/