What you need to know about Docker 1.13

Docker 1.13 is launching soon, and the release brings some exciting changes.

Apart from the slew of small bug fixes and touchups that accompany any major release, Docker 1.13 is characterized by increased Windows support (more Windows log drivers, overlay network support for Windows Server 2016, swarm-mode for Windows), enhanced compatibility (new client can talk to older servers), and a more user-friendly approach to trying experimental features.

Still, reading through the complete list of features and changes can be tedious. Luckily, InfoSiftr’s Tianon Gravi (a Docker core maintainer), has done the hard work for us. He’s combed through the changes and selected 17 of the most interesting.

Here are some of the most interesting changes in Docker 1.13:

  • New capability to “specify images used as a cache source on build” (docker build –cache-from)
  • External storage now allowed for registry credentials
  • More Windows log drivers (syslog, fluentd)
  • swarm-mode overlay networks can be optionally “attachable” from `docker run`
  • swarm-mode services can publish ports on the host running the container rather than load-balanced publish over the whole swarm
  • Overlay network support for Windows Server 2016
  • `docker plugin …` (high level plugin management interface)
  • `docker stack deploy` (`docker-compose.yml` to services — v3 only)
  • New client can talk to older servers
  • Experimental as a daemon flag rather than a separate binary/package (for testing out new/in-progress features that aren’t ready for full public consumption yet)
  • `docker run –rm` in the daemon instead of the client (more reliable/flexible)
  • `docker stats`+`docker top` support in Windows
  • Experimental Prometheus metrics endpoint
  • ‘prune` subcommands for removing unused resources (stopped containers, dangling images, unused volumes/networks, etc)
  • swarm-mode secret management
  • swarm-mode for Windows
  • `docker daemon` officially deprecated in favor of `dockerd` (separate daemon binary)

Exciting stuff. But before you upgrade to Docker 1.13, please note the warning from Victor Vieux: “in Docker 1.13, the managed plugin api changed, as compared to the experimental version introduced in Docker 1.12. You must uninstall plugins which you installed with Docker 1.12 before upgrading to Docker 1.13.”

Please join us in celebrating this latest release. Docker 1.13 represents a lot of work by a lot of talented people. It’s another step toward making Docker more accessible, efficient, and useful for everyone.

(For more information, check out Vieux’s complete notes about the pending release, including complete instructions for removing Docker 1.12 plugins.)


About the Author: