mirror of https://github.com/docker/docs.git
Update upgrade.md (#9548)
Fixed typo. I think I fixed broken link. Same link was working just below the fixed one. I copied text from there.
This commit is contained in:
parent
73e5ac3fd7
commit
50100ab8e8
|
|
@ -33,7 +33,7 @@ deployed. As part of this, services using HRM labels are inspected.
|
||||||
3. The HRM service is removed.
|
3. The HRM service is removed.
|
||||||
4. The `ucp-interlock` service is deployed with the configuration created.
|
4. The `ucp-interlock` service is deployed with the configuration created.
|
||||||
5. The `ucp-interlock` service deploys the `ucp-interlock-extension` and
|
5. The `ucp-interlock` service deploys the `ucp-interlock-extension` and
|
||||||
`ucp-interlock-proxy-services`.
|
`ucp-interlock-proxy` services.
|
||||||
|
|
||||||
The only way to rollback from an upgrade is by restoring from a backup taken
|
The only way to rollback from an upgrade is by restoring from a backup taken
|
||||||
before the upgrade. If something goes wrong during the upgrade process, you
|
before the upgrade. If something goes wrong during the upgrade process, you
|
||||||
|
|
@ -90,7 +90,7 @@ don't have any configuration with the same name by running:
|
||||||
* If either the `ucp-interlock-extension` or `ucp-interlock-proxy` services are
|
* If either the `ucp-interlock-extension` or `ucp-interlock-proxy` services are
|
||||||
not running, it's possible that there are port conflicts.
|
not running, it's possible that there are port conflicts.
|
||||||
As a workaround re-enable the layer 7 routing configuration from the
|
As a workaround re-enable the layer 7 routing configuration from the
|
||||||
[UCP settings page](deploy/index.md). Make sure the ports you choose are not
|
[UCP settings page](index.md). Make sure the ports you choose are not
|
||||||
being used by other services.
|
being used by other services.
|
||||||
|
|
||||||
## Workarounds and clean-up
|
## Workarounds and clean-up
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue