Use a bash shell variable to run support dump at the same revision as
the cluster is running. This is a copy-paste convenience for users in offline environments that might not be running the latest version.
Signed-off-by: Trapier Marshall <trapier.marshall@docker.com>
reconfigure-db command needs to be run without the --emergency-repair flag, because you should only use that when a table has lost a majority of replicas.
Please refer to https://github.com/docker/escalation/issues/943
* Adding "windows" label to Windows node.
Additional steps to add label to Windows Nodes. This will allow admin to filter Windows node when creating a service like this.
`docker service create --constraint engine.labels.os==windows --name winonly microsoft/nanoserver` The same steps are on this article: https://success.docker.com/article/how-can-i-assign-a-service-to-windows-nodes-only
* wrong environment variable fixed.
--existing-config is a flag that uses the latest UCP config found in the
environment and does not accept a config as a flag variable. This
should help clarify that.
Signed-off-by: Kyle Squizzato <kyle.squizzato@docker.com>
Replace all occurrences of
```foo
{% raw %}
bar
{% endraw %}
```
(which generates spurious empty lines in the rendered pre block) with
{% raw %}
```foo
bar
```
{% endraw %}
Also, fix some occurrences where the raw section is too large and
prevented interpretation of Jekyll directives.
This is the syntax used in the documentation of Jekyll itself:
https://raw.githubusercontent.com/jekyll/jekyll/master/docs/_docs/templates.md
FTR, done with two perl substitutions:
'^([\t ]*```[^\n]*
)([ \t]*\{% raw %\}[^\n]*
)' '$2$1'
and
'^([ \t]*\{% endraw %\}[^\n]*
)([\t ]*```[^\n]*
)' '$2$1'
and manually tweaks. A mechanical check would be most useful.
Signed-off-by: Akim Demaille <akim.demaille@docker.com>
* HRM and Window Servers
Note:- Windows Server doesn't support Swarm Mode Routing Mesh yet (not considering Windows Server version 1709 which will be out soon). This means the hrm service is exposed only through the manager node's ip (since Windows Server cannot be a manager node). Therefore the DNS entry for the host name ('wordpress.example.org' in this example) should be mapped to the manager node and not to any of the Windows worker nodes.
* HRM with Windows Server
HRM with Windows Server