This is the first in a series of articles we are publishing to provide more details on Docker Desktop Enterprise, which we announced at DockerCon Barcelona. Keep up with the latest Docker Desktop Enterprise news and release updates by signing up for the Docker Desktop Enterprise announcement list.
Docker’s engineers have been hard at work completing features and getting everything in ship-shape (pun intended) following our announcement of Docker Desktop Enterprise, a new desktop product that is the easiest, fastest and most secure way to develop production-ready containerized applications and the easiest way for developers to get Kubernetes running on their own machine.
In the first post of this series I want to highlight how we are working to bridge the gap between development and production with Docker Desktop Enterprise using our new Version Packs feature. Version Packs let you easily swap your Docker Engine and Kubernetes orchestrator versions to match the versions running in production on your Docker Enterprise clusters. For example, imagine you have a production environment running Docker Enterprise 2.0. As a developer, in order to make sure you don’t use any APIs or incompatible features that will break when you push an application to production you would like to be certain your working environment exactly matches what’s running in Docker Enterprise production systems. With Docker Desktop Enterprise you can easily do that through the use of Version Packs. Later, when the platform operators decide to upgrade production systems to Docker Enterprise 2.1, all that needs to be done in Docker Desktop Enterprise is to add the Enterprise 2.1 version pack and easy as that, you’re in sync. If you have different environments, you can even switch back forth, all with a single click.
We’re building Docker Desktop Enterprise as a cohesive extension of the Docker Enterprise container platform that runs right on developers’ systems. Developers code and test locally using the same tools they use today and Docker Desktop Enterprise helps to quickly iterate and then produce a containerized service that is ready for their production Docker Enterprise clusters.
In future previews, we’ll share more details on how Docker Desktop Enterprise capabilities can be centrally administered and controlled; using the Application Designer to create an application with zero Docker CLI commands; and how to ensure developers start building with safe, approved templates. Sign up for the Docker Desktop Enterprise announcement list or keep watching this blog for more in the coming weeks.
To learn more: