Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Cloud link to Azure topics #2713

Merged
merged 16 commits into from
May 2, 2017
Merged
Prev Previous commit
added more code examples for Azure and AWS
Signed-off-by: Victoria Bialas <victoria.bialas@docker.com>
  • Loading branch information
Victoria Bialas committed May 2, 2017
commit 04a28da45d0f4b6445caa5c960c53fb1ebf407a3
15 changes: 13 additions & 2 deletions docker-cloud/cloud-swarm/connect-to-swarm.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,11 +39,22 @@ local Docker instance, which connects to a manager node on the target swarm.

6. Now, you can run `docker node ls` to verify that the swarm is running.

Here is an example of `docker node ls` output for a swarm running one manager and two workers on **Amazon Web Services**.

```
$ docker node ls
ID HOSTNAME STATUS AVAILABILITY MANAGER STATUS
dhug6p7arwrm3a9j62zh0a0hf ip-172-31-23-167.us-west-1.compute.internal Ready Active
xmbxtffkrzaveqhyuouj0rxso ip-172-31-4-109.us-west-1.compute.internal Ready Active
yha4q9bleg80kvbn9tqgxd69g * ip-172-31-24-61.us-west-1.compute.internal Ready Active Leader
```

Here is an example of `docker node ls` output for a swarm running one manager and two workers on **Microsoft Azure Cloud Services**.

```
$ docker node ls
ID HOSTNAME STATUS AVAILABILITY MANAGER STATUS
6uotpiv8vyxsjzdtux13nkvj4 swarm-worker000001 Ready Active
8j3e54j3vv16scrrvcyg5de2w swarm-worker000002 Ready Active
6uotpiv8vyxsjzdtux13nkvj4 swarm-worker000001 Ready Active
qmvk4swo9rdv1viu9t88dw0t3 swarm-worker000000 Ready Active
w7kgzzdkka0k2svssz1dk1fzw * swarm-manager000000 Ready Active Leader
```
Expand Down