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

removed incorrect description of how to link to a service #4156

Merged
merged 1 commit into from
Aug 10, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 2 additions & 7 deletions docker-cloud/apps/load-balance-hello-world.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ ready to continue and launch our web service.

1. Click **Services** in the left hand menu, and click **Create**.

3. Click the **rocket icon** and select the **dockercloud/hello-world** image.
3. Click the **rocket icon** at the top of page, and select the **dockercloud/hello-world** image.

![](images/lbd-hello-world-jumpstart.png)

Expand Down Expand Up @@ -96,8 +96,7 @@ browser and view the **dockercloud/hello-world** web page. Note the hostname fo

![](images/lbd-hostname-1.png)

3. Click other endpoints and check the hostnames. You'll see different hostnames
which match the container name (web-2, web-3, and so on).
3. Click other endpoints and check the hostnames. You'll see different hostnames which match the container name (web-2, web-3, and so on).

## Launch the load balancer

Expand Down Expand Up @@ -193,7 +192,3 @@ Docker Cloud automatically assigns a DNS endpoint to all services. This endpoint
routes to all of the containers of that service. You can use the DNS endpoint to
load balance your load balancer. To learn more, read up on [service
links](service-links.md).

You can try this by pointing your web browser to
*servicename.username.svc.dockerapp.io* or using *dig* or *nslookup* to see how
the service endpoint resolves.