mirror of
https://github.com/docker/docs.git
synced 2026-04-02 01:08:53 +07:00
a4f5e30249
* Reword lots of instances of 'will' * Reword lots of instances of won't * Reword lots of instances of we'll * Eradicate you'll * Eradicate 'be able to' type of phrases * Eradicate 'unable to' type of phrases * Eradicate 'has / have to' type of phrases * Eradicate 'note that' type of phrases * Eradicate 'in order to' type of phrases * Redirect to official Chef and Puppet docs * Eradicate gratuitous 'please' * Reduce use of e.g. * Reduce use of i.e. * Reduce use of N.B. * Get rid of 'sexagesimal' and correct some errors
44 lines
1.7 KiB
Markdown
44 lines
1.7 KiB
Markdown
---
|
|
description: Upgrading your stack
|
|
keywords: aws, amazon, iaas, tutorial
|
|
title: Docker for AWS upgrades
|
|
---
|
|
|
|
To upgrade, apply a new version of the AWS Cloudformation template that powers
|
|
Docker for AWS. Depending on changes in the next version, an upgrade involves:
|
|
|
|
* Changing the AMI backing manager and worker nodes (the Docker engine
|
|
ships in the AMI)
|
|
* Upgrading service containers
|
|
* Changing the resource setup in the VPC that hosts Docker for AWS
|
|
|
|
## Prerequisites
|
|
|
|
* We recommend only attempting upgrades of swarms with at least 3 managers.
|
|
A 1-manager swarm can't maintain quorum during the upgrade.
|
|
|
|
* You can only upgrade one version at a time. Skipping a version during
|
|
an upgrade is not supported. Downgrades are not tested.
|
|
|
|
## Upgrading
|
|
|
|
New releases are announced on [Release Notes](release-notes.md) page.
|
|
|
|
To initiate an update, use either the AWS Console or the AWS cli to initiate a
|
|
stack update. Use the S3 template URL for the new release and complete the
|
|
update wizard. This initiates a rolling upgrade of the Docker swarm, and
|
|
service state is maintained during and after the upgrade. Appropriately
|
|
scaled services should not experience downtime during an upgrade.
|
|
|
|
|
|
|
|
Single containers started (for example) with `docker run -d` are
|
|
**not** preserved during an upgrade. This is because they're not Docker Swarm
|
|
objects, but are known only to the individual Docker engines.
|
|
|
|
## Changing instance sizes and other template parameters
|
|
|
|
In addition to upgrading Docker for AWS from one version to the next you can
|
|
also use the AWS Update Stack feature to change template parameters such as
|
|
worker count and instance type. Changing manager count is **not** supported.
|