Skip to content

Set more explicit version of the Docker and DinD images

Tomasz Maczukin requested to merge update-docker-dind-1903-blog-post into master

Update for !26608 (merged).

With !26608 (merged) we've added a description of how to resolve recent problems with new version of Docker DinD image. As part of the description we've pointed that users should use explicit version numbers, instead of relaying on :stable-dind or :dind. This is to prevent unwanted and untested upgrades, that may bring breaking changes.

Unfortunately, XX.YY-dind is not the most explicit pattern of version. And today Docker released another version in 18-dind and 19-dind branches, that breaks our configurations.

This MR adds an update, changing all 19.03 versions in examples to 19.03.0. This is done for two reasons:

  1. This is the most explicit version that can be set (19.03 will be still a floating version, pointing the latest 19.03.x, which is what we want to prevent).
  2. This is the version that works with the configuration described in this blog post.

Merge request reports