What's Missing from the Open Container Initiative?

by Sean Michael Kerner

Alex Polvi, CEO of CoreOS, discusses what's wrong and what's right with the Open Container Initiative.

The Open Container Initiative was officially announced on June 22 as the Open Container Project, and it has been steadily evolving over the last six months. The Open Container Initiative (OCI) name first emerged in June, along with details about the organization's efforts to help standardize containers.

In a video interview, Alex Polvi, CEO of CoreOS, discusses what is right with OCI and what's still missing. Alex Polvi Polvi noted that CoreOS started the app container specification (appc), which is an effort to have a well-defined specification of what a container is and how it runs on a system.

"OCI is very narrowly scoped. Its scope is so narrow that I do wonder how it will work over time," Polvi said. "Essentially what it defines now is the component represented by RunC, which is the way that you execute a container."

Polvi explained that in his view the level of interoperability is really now just across vendors, rather than at a true standards level.

"It's sort of like the web browser vendors sharing WebKit, when really what you want is HTML5 to be standardized," Polvi said. "You want the thing the end user consumes to be standardized."

Watch the video with Alex Polvi below:

Sean Michael Kerner is a senior editor at ServerWatch and InternetNews.com. Follow him on Twitter @TechJournalist.

Follow ServerWatch on Twitter and on Facebook

This article was originally published on Monday Dec 7th 2015
Mobile Site | Full Site