Specify that all nodes need to be the same exact Docker version for production UCP clusters #1465
Labels
Milestone
Comments
|
UCP could issue a warning in the gui/cli too. "engine version discrepancy detected. Please upgrade all engines to the same version." |
aaronlehmann
pushed a commit
to aaronlehmann/docker.github.io
that referenced
this issue
Feb 14, 2017
* closes docker#938 * closes docker#1252 * closes docker#1318 * closes docker#448 * closes docker#1465 * closes docker#1317 * closes docker#912 * closes docker#1473
aaronlehmann
pushed a commit
to aaronlehmann/docker.github.io
that referenced
this issue
Feb 14, 2017
* closes docker#938 * closes docker#1252 * closes docker#1318 * closes docker#448 * closes docker#1465 * closes docker#1317 * closes docker#912 * closes docker#1473
mdlinville
changed the title
constanzekratel
added a commit
to constanzekratel/docker.github.io
that referenced
this issue
Apr 19, 2017
…cker version for production UCP clusters docker#1465 Just made a minor correction as part of fixing this bug. Added "with" to comply and also added "exact" to emphasize the importance of running the same version. Other than that this bug already appears to have been fixed.
|
It looks like this one has already been fixed. Made a minor change to the page and added "exact" to same version to emphasize importance. See PR #2885 |
constanzekratel
added a commit
to constanzekratel/docker.github.io
that referenced
this issue
Apr 19, 2017
Added a note saying that the version of Docker CS Engine must be the same for all nodes. docker#1465
|
Submitted a new PR for the same fix for UCP version 2.1: #2924 |
joaofnfernandes
pushed a commit
that referenced
this issue
Apr 19, 2017
…ersion for production UCP clusters #1465 Just made a minor correction as part of fixing this bug. Added "with" to comply and also added "exact" to emphasize the importance of running the same version. Other than that this bug already appears to have been fixed.
johndmulhausen
pushed a commit
that referenced
this issue
Apr 19, 2017
|
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. /lifecycle locked |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
File: datacenter/ucp/2.0/guides/installation/plan-production-install.md
Can we specify on this page that for production UCP clusters, unless a temporary upgrade is occurring, all engines need to be the same x.y.z version number? We have seen several situations where this has caused issues and it should be documented.
The text was updated successfully, but these errors were encountered: