Docker 1.12 Advances Mac and Windows Desktop Editions
Lots of container technology news is rolling in this week. Mesosphere announced support for the Confluent Platform for data streaming management, and heralded that "the time is now for Container 2.0."
Meanwhile, many more users are taking to Docker's recently unveiled version 1.12 of its core software-containerization system today, accompanied by the first full desktop editions of the software for development on Mac and Windows machines.
Docker for Mac and Docker for Windows have graduated from beta and are now stable and ready for production.
Improvements include:
- Faster and more reliable – native development environment using hypervisors built into each operating system. (No more VirtualBox!)
- Improved Docker tools integration – all the Docker tools you need to develop locally are bundled in the app.
- Improved development flow – Volume mounting for your code and data, and easy access to running containers on the localhost network. In-container debugging with supported IDEs also help you live debug projects, and iterate code quicker with less effort.
- Enterprise network support that lets Docker for Mac and Windows work easily with VPNs.
- All the new features available in Docker Engine 1.12.
- Automatic updates, with different channels for stable and beta.
You can also read a post on the architecture and features in Docker 1.12. It features easy to use built-in orchestration, and end-to-end encryption. And, if you are new to Docker, try a 10-minute online tutorial.
Docker has added:
"Docker for Mac and Windows are available from 2 channels – stable and beta. New features and bug fixes will go out first in auto-updates to users in the beta channel. Updates to the stable channel are much less frequent and happen in sync with major and minor releases of the Docker engine. Only features that are well-tested and ready for production are added to the stable channel releases.
If you want the latest and greatest Docker experimental builds, use the beta channel. If you want fewer updates and can wait until new features and enhancements are tested and production-ready, use the stable channel."