Docker 1.6 Emerges As A Platform - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IoT
IoT
Cloud // Infrastructure as a Service
News
4/17/2015
10:30 AM
Connect Directly
Twitter
RSS
E-Mail
100%
0%

Docker 1.6 Emerges As A Platform

Several components of Docker, including Engine, Registry, and orchestration tools, have been upgraded together as a platform.

10 Linux Distros You Need To Know
10 Linux Distros You Need To Know
(Click image for larger view and slideshow.)

The Docker container formatting system, with its varied tools, is being pulled together into a more uniform platform for container management, with the issuance of Release 1.6 on April 16.

As a result, its emphasis is shifting from container construction for developers to container management for operations. Performance is important to developers, but it's even more important in production settings, where certain actions are going to be repeated thousands of times.

The Docker Engine now has a different protocol for interacting with the Docker Registry when a container image is sought for launch.

In the past, a "pull" request would lead to the container image's operating system layer being downloaded, followed by needed libraries, application logic, database connections, and related dependencies, in a sequential process. Now that process can take place with the layers downloaded in parallel, simultaneously, then shuffled into correct image order at the destination.

That's thanks to the "complete rewrite" of the Registry for the 2.0 version, along with a new Registry API. The upgraded Docker Engine 1.6 works with the Registry 2.0 API.

(Image: FraukeFeind via Pixabay)

(Image: FraukeFeind via Pixabay)

In addition, the new API allows more granularity to Docker images, with each layer given a unique identifier. If one layer only needs to be updated, that layer can be accessed in the Hub and downloaded, although all the layers in the stack that come after it will need to be downloaded as well, explained Scott Johnston, senior vice president of product at Docker.

[Read about Docker's recent additions.]

The process can speed a container image update. "You just update those layers that need it." The way containers are formatted is to put down layers, so that any successive layer meets any dependencies in the layers below it. Once a layer is updated, the layers above it must be updated as well, in case any of the operations above it have changed as a result of that change.

In an interview, Johnston said there have been 300 million downloads of Docker container images from the DockerHub since it was launched in beta in April 2014. The images represent containerized applications that someone needs in his or her data center.

Speeding up those downloads will make Docker more useful in production settings.

Part of what's driving the activity is the ability to access previously used components at Docker Hub Official Repos, which include basic services such as specific Linux distributions, databases, and applications servers, already available in a container.

Johnston said before the announcement that he expected figures reflecting how much faster the downloads would be to be posted in a blog on the Docker Engine 1.6 announcement. The blog, once posted Thursday, only cited "dramatically faster" downloads.

Docker Engine 1.6 is "backward compatible" with previous versions of the API so that existing Docker systems don't need to be modified, Johnston noted.

In Thursday's launch of the second Docker Compose tool, Release 1.2, has been revised to make it possible to define and run multi-container applications, with the containers sometimes operating in separate environments but still linked. Compose "makes it easy to share configurations between different environments" and use one configuration for development and test and another for production.

Additional changes in the 1.6 release of Docker are referenced in the April 16 blog.

In the past, Docker has risked splintering its approach to its customers by introducing container formatting, orchestration, and cluster management products in rapid-fire succession, with various user interactions and interfaces. From this point forward, it is consolidating announcements into a single event, upgrading Docker Engine, Registry, Compose, Machine, and Swarm at the same time "for a more consistent user experience."

"By synchronizing our releases, we are simplifying the evaluation and deployment process and enabling the community to benefit from the integrated value that we're building for them," said Solomon Hykes, CTO and chief architect of Docker.

At two-years-old, Docker is trying to become a mature software company.

Attend Interop Las Vegas, the leading independent technology conference and expo series designed to inspire, inform, and connect the world's IT community. In 2015, look for all new programs, networking opportunities, and classes that will help you set your organization’s IT action plan. It happens April 27 to May 1. Register with Discount Code MPOIWK for $200 off Total Access & Conference Passes.

Charles Babcock is an editor-at-large for InformationWeek and author of Management Strategies for the Cloud Revolution, a McGraw-Hill book. He is the former editor-in-chief of Digital News, former software editor of Computerworld and former technology editor of Interactive ... View Full Bio

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Ashu001
50%
50%
Ashu001,
User Rank: Ninja
4/29/2015 | 4:27:38 PM
Re: Paying attention to operational details
Li.

I have just started demo-testing Docker and the potential is HUGE no doubt about it.

Still I would like to hear from a sceptic like what all could go wrong here.

Its always good to hear from experts in this space regarding what one needs to be wary/careful about today.
Li Tan
50%
50%
Li Tan,
User Rank: Ninja
4/18/2015 | 3:25:39 PM
Re: Paying attention to operational details
I think if the process can run smoothly, it would still work. Otherwise it will create additional burdens for operational tasks.
Charlie Babcock
50%
50%
Charlie Babcock,
User Rank: Author
4/17/2015 | 8:43:09 PM
Paying attention to operational details
The change in the image download process shows how much more sophisticated Docker is becoming about the needs of its operational users, as well as developers.
News
Think Like a Chief Innovation Officer and Get Work Done
Joao-Pierre S. Ruth, Senior Writer,  10/13/2020
Slideshows
10 Trends Accelerating Edge Computing
Cynthia Harvey, Freelance Journalist, InformationWeek,  10/8/2020
News
Northwestern Mutual CIO: Riding Out the Pandemic
Jessica Davis, Senior Editor, Enterprise Apps,  10/7/2020
White Papers
Register for InformationWeek Newsletters
Video
Current Issue
[Special Report] Edge Computing: An IT Platform for the New Enterprise
Edge computing is poised to make a major splash within the next generation of corporate IT architectures. Here's what you need to know!
Slideshows
Flash Poll