Docker Inc. today set course for a new destination that will see the container pioneer capitalize on Kubernetes complexity as it aims to win the hearts and favorability of developers. 

The rise of Kubernetes as the de facto container orchestration platform has proven to be a challenge for many vendors, even rendering some competitors obsolete. Perhaps no one has felt the Kubernetes boom more so than Docker Inc., which imploded last November. To save its ship from being docked for good, Docker Inc. sold its halo Enterprise business and associated intellectual property to Mirantis. The move was the first phase of its corporate restructuring.

The next phase was announced today and includes a new focus on its Docker Desktop and Docker Hub assets. Justin Graham, VP of products at Docker Inc., explained in a blog post that this will see the company “partnering with the ecosystem” as it aims to make Docker Hub the “nexus for all integrations, configuration, and management of the application components.”  

The firm’s container platform, which is known as simply Docker, was developed to address the problem of running and replicating code on any platform. However, as containers have become ubiquitous, Graham told SDxCentral that the problem space has “shifted up the stack.”

“We see this in the middle space between where source control ends and production runtime of applications begins,” Graham said. The “middle space” Graham is referring to is also known as middleware, or the software glue that lies between an operating system and the applications running on it.  

Docker Inc. hopes to cash in on this middle space, which Graham said has yet to be standardized or “wholesale resolved.” The move is also a shift for Docker Inc. in turning to its customers and community to drive product evolution through participation in prioritizing feature requests, serving as a complimentary platform to  GitHub, GitLab, and Atlassian.

"We think there's a unique opportunity for Docker, through Docker Desktop, Docker Hub and our open source work, to help make that middle space and code-to-cloud space incredibly efficient, simple, cost effective for development teams and individual developers,” he added. 

Larry Carvalho, research director for IDC’s platform-as-a-service (PaaS) practice, told SDxCentral that while the move is Docker Inc.’s first after the Enterprise sale, it was “not too late but could have come earlier.” Carvalho called Docker Inc.’s decision to focus on developers a “good approach since there is a high need for tools to improve developer productivity.” 

“Building a pipeline is not simple and consuming such a service with a subscription model will be attractive,” he added.

Redmonk co-founder Stephen O’Grady said Docker Inc.’s “code to cloud” path is still “one with holes” and represents an area for the company to make a potential impact.

Docker Inc. was indeed foundational in the development of the current container ecosystem, making the Docker brand one of the most prominent names in the cloud container ecosystem. While perhaps shallow, that name recognition remains a significant advantage. 

“If Docker can quickly get some case studies and spread the word of developer success using their platform, there may be a growth in adoption,” Carvalho said. “Also, support of multiple public cloud providers will be attractive for customers not keen on putting all their eggs in one public cloud platform and want portability.”