Clarify upgrading documentation #2039
Merged
Conversation
This file contains hidden or 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
|
|
||
| ## General Information | ||
|
|
||
| Upgrading is not advised on running apps. Stop them before with `dokku ps:stop <app>`. |
Member
There was a problem hiding this comment.
I would think so. I wouldn't upgrade on a running "production" host. Specifically when we require a particular version of docker that could potentially cause that package to be upgraded would cause the docker daemon to restart. Thus, resulting in downtime.
Member
There was a problem hiding this comment.
It should be noted that docker >=1.11 promises your containers don't need to be restarted if the docker daemon is restarted. However live upgrades in a production level environment (without fail overs) are not recommended.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Updated upgrading instructions from the trouble spots I had in upgrading with @michaelshobbs's advice.