docker: Update version from 1.12.3 to 17.03.0-ce #304
Merged
+5
−5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Release notes [1][2][3]: > ### 1.13.0 (2017-01-18) ### > > **IMPORTANT**: 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. You can uninstall plugins using the > `docker plugin rm` command. > > If you have already upgraded to Docker 1.13 without uninstalling > previously-installed plugins, you may see this message when the Docker > daemon starts: > > ``` > Error starting daemon: json: cannot unmarshal string into Go value of > type types.PluginEnv > ``` > > To manually remove all plugins and resolve this problem, take the > following steps: > > * Remove plugins.json from: `/var/lib/docker/plugins/`. > * Restart Docker. Verify that the Docker daemon starts with no errors. > * Reinstall your plugins. > > […] > ### 1.13.1 (2017-02-08) ### > > **IMPORTANT**: On Linux distributions where `devicemapper` was the > default storage driver, the `overlay2`, or `overlay` is now used by > default (if the kernel supports it). To use devicemapper, you can > manually configure the storage driver to use through the > `--storage-driver` daemon option, or by setting "storage-driver" in > the `daemon.json` configuration file. > > […] > ### v17.03.0-ce (2017-03-01) ### > > **IMPORTANT**: Starting with this release, Docker is on a monthly > release cycle and uses a new YY.MM versioning scheme to reflect this. > Two channels are available: monthly and quarterly. Any given monthly > release will only receive security and bugfixes until the next monthly > release is available. Quarterly releases receive security and bugfixes > for 4 months after initial release. This release includes bugfixes for > 1.13.1 but there are no major feature additions and the API version > stays the same. Upgrading from Docker 1.13.1 to 17.03.0 is expected > to be simple and low-risk. Tested on *keineahnung*: ``` $ sudo docker version Client: Version: 17.03.0-ce API version: 1.26 Go version: go1.7.5 Git commit: v17.03.0-ce Built: Mon Mar 6 10:56:34 2017 OS/Arch: linux/amd64 Server: Version: 17.03.0-ce API version: 1.26 (minimum version 1.12) Go version: go1.7.5 Git commit: v17.03.0-ce Built: Mon Mar 6 10:56:34 2017 OS/Arch: linux/amd64 Experimental: false ``` [1] https://github.com/docker/docker/releases/tag/v1.13.0 [2] https://github.com/docker/docker/releases/tag/v1.13.1 [3] https://github.com/docker/docker/releases/tag/v17.03.0-ce
|
If there is a better way to get the full version with all underscores replace by dashes, please tell me. |
|
Whats wrong with the two variants you used? and I'd prefer the first one, because it only requires knowledge of bash and not knowledge of bee to understand what it is doing. But I know, opinions are parted over that. would do as well (replacing only the first |
Sign in
to join this conversation on GitHub.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tested on keineahnung.