Docker 1.11 ties its fate to Open Container Initiative
Docker recently announced that it has tied its fate to Open Container Initiative —Docker Engine 1.1 is the first release built on runC and containerd and the first OCI-compliant runtime.
Docker has been helping advance the work of the Open Container Initiative to make it more effortlessly available to more users. It all started in December last year, when Docker introduced containerd, a daemon to control runC, as part of their effort to break out Docker into small reusable components. With the newly-released 1.11, Docker Engine is now built on containerd, which means that all Docker users are now using OCI too. According to the Docker 1.11 announcement, “this is the first OCI-compliant runtime and demonstrates the progress since donating our industry-standard container format and runtime under the Linux Foundation in June of last year.”
Open Container Initiative launches project to establish a container image format specification
The Open Container Initiative has just launched a project to establish a container image format specification —the project is tasked with developing a software shipping container image format specs with security and federated naming as key components. “The OCI was formed in a vendor-neutral setting with industry leaders to come together on container standards,” said Chris Aniszczyk for the Open Container Initiative at The Linux Foundation. The OCI Image Format project helps the organization to celebrate one essential milestone, namely to develop a standard image format that can be widely used by vendors and users.
Dr. Diogo Monica, member of the OCI Technical Oversight Board and Security Lead at Docker, emphasized that “Docker and its partners have been working towards decoupling and securing the container image format” over the past few years and expressed her excitement over the close working relationship between Docker and the OCI technical community —with the aim to deliver an image format which can be used in a wide range of scenarios.
The OCI project is starting with Docker v.2.2 image format as its base, which should result in minimal effort to converge the two formats. According to a blog post by CoreOS’ Jonathan Boulle, “soon both Docker and rkt will support a shared, standard container image format, with an open specification house at the OCI.”
The goal of the Open Container Initiative Image Specs is to allow developers to package and sign application containers, then run them in a collection of container engines. Teams will now be able to choose the build tools and execution scheme which best meets their needs.