The Open Container Initiative at 1.0: the current state of container standards

The Open Container Initiative was formed as a joint effort by leaders in the container ecosystem to create a stable industry standard for containers image and runtime specifications. Recently, the OCI runtime and image specifications hit version 1.0. The image spec defines a standard container image format that can be executed by runtimes conforming to the open runtime specification, aiming to make container images truly portable.

In this talk, Brandon Philips, CTO at CoreOS, will discuss the implications of a stable industry standard for future application container development, the importance of community buy-in to fully reap the benefits of a collaborative and open system, and the next steps for the community standards.

Vorkenntnisse

The audience should be comfortable with the various container image and runtime specifications.

Lernziele

* Why standards are needed in the container ecosystem
* What elements the standards are relevant to
* What’s next for the OCI specifications

Speaker

 

Brandon Philips
Brandon Philips is cofounder and chief technology officer of CoreOS. He leads teams building modern server infrastructure open source projects like Container Linux and enterprise products, like CoreOS Tectonic, the enterprise Kubernetes stack, and Quay, a private container image registry. He guides technical direction of cloud native technologies in the Cloud Native Computing Foundation. He leads the Technical Oversight Board of the Open Container Initiative, guiding open source communities building modern infrastructure and the technical future of projects essential to cloud native infrastructure stacks. Prior to CoreOS, he worked at Rackspace hacking on cloud monitoring and was a Linux kernel developer at SUSE. As a graduate of Oregon State's Open Source Lab, he is passionate about open source technologies and is a member of Oregon State's Council of Outstanding Early Career Engineers.

CC-Newsletter

Sie möchten über die Continuous Lifecycle und die ContainerConf auf dem Laufenden gehalten werden?

 

Anmelden