CoreOS Taking on Docker at Its Own Game Page 2
CoreOS Taking on Docker at Its Own Game
At the beginning of May, Google announced it is integrating rkt as a configurable container runtime into Kubernetes. That means Kubernetes will be able to use rkt to run containers — both App Container images and Docker images — without the need for any Docker software.
To ensure the App Container specification remains a community-led effort, CoreOS also announced that the project has established a governance policy and elected several new community maintainers: Vincent Batts of Red Hat, Tim Hockins of Google, and Charles Aylward of Twitter.
And just to emphasize that CoreOS is taking on Docker at its own game, the company has also beefed up its Quay hosted-container registry, an alternative to Docker Hub.
The improvements include a new user interface, a new search system, faster build times, and a "time machine" feature that allows companies to revert images to previous states from the last two weeks if new images cause unwanted issues.
The company has promised to invest heavily in Quay both as a standalone product and as a feature of its commercial Tectonic offering.
Docker's lead in the container space has looked unstoppable up to now — and to an extent it continues to do so. But with Google, VMware and many other companies lining up to support CoreOS and rkt, it would be foolish to assume that the container field will continue, indefinitely, to be a one-horse race.
Paul Rubens is a technology journalist and contributor to ServerWatch, EnterpriseNetworkingPlanet and EnterpriseMobileToday. He has also covered technology for international newspapers and magazines including The Economist and The Financial Times since 1991.
Read more on "Real World Open Source" »