Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

OCI Announces New Project to Advance Container Standardization

DZone's Guide to

OCI Announces New Project to Advance Container Standardization

To encourage wide adoption of container tech, the Open Container Initiative plans to create rules on how container images should be built.

· Cloud Zone ·
Free Resource

Discover a centralized approach to monitor your virtual infrastructure, on-premise IT environment, and cloud infrastructure – all on a single platform.

Recently, the Open Container Intiative announced the new Image Spec Format project, an expansion of the OCI Runtime Spec project, which set rules on how to run containers. The Image Spec Format aims to provide users with rules on how container images should be built, focusing mostly on serialization, security (hasning and signing), and federated naming. 

According to the Initiative's GitHub page, the project was started because: 

We are seeing many independent implementations of container image handling including build systems, registries, and image analysis tools. As an organization we would like to encourage this growth and bring people together to ensure a technically correct and open specification continues to evolve reflecting the OCI values.

The long term goal is to introduce the ability to run containers across a variety of runtimes, which will be achieved in combination with the Runtime Spec project. The Image Spec Format project is based on Docker 2.2 (which in turn is heavily influenced by the appc spec), and is supported by a variety of vendors including Docker, Mesosphere, Rancher Labs, VMware, Dell, and Red Hat. You can find the full press release here, and find the Image Spec Format GitHub page here

Learn how to auto-discover your containers and monitor their performance, capture Docker host and container metrics to allocate host resources, and provision containers.

Topics:
docker ,containers ,images

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}