Merge pull request docker#222 from andreykovalenko/issue-221-fix

fix issue 221 - incorrect port mapping

Author: Mano Marks

developer-tools/nodejs/porting/4_single_host_networking.md

@@ -107,7 +107,7 @@ Run db and application containers in the new bridge network
 
 ```
 $ docker run --name mongo --net mongonet -d mongo:3.2
-$ docker run --name app --net mongonet -p “8000:80” -d -e “MONGO_URL=mongodb://mongo/messageApp” message-app:v1
+$ docker run --name app --net mongonet -p 8000:1337 -d -e “MONGO_URL=mongodb://mongo/messageApp” message-app:v1
 ```
 
 Note: MONGO_URL environment variable directly uses **mongo** container’s name
@@ -154,7 +154,7 @@ services:
   app:
     image: lucj/message-app
     ports:
-      - "80"
+      - "1337"
     links:
       - mongo
     depends_on:
@@ -221,7 +221,7 @@ services:
   app:
     image: message-app
     expose:
-      - "80"
+      - "1337"
     links:
       - mongo
     depends_on:

developer-tools/nodejs/porting/6_deploy_on_swarm.md

@@ -1,6 +1,6 @@
 # Deployment on a Docker Swarm
 
-As for the multi Docker host environment, a Docker Swarm requires a key value store to gather the nodes / containers configurations and states. 
+As for the multi Docker host environment, a Docker Swarm requires a key value store to gather the nodes / containers configurations and states.
 
 ## Creation of a key-value store
 
@@ -35,7 +35,8 @@ demo0
 $ docker-machine create \
  -d virtualbox \
 --swarm \
---swarm-discovery="consul://$(docker-machine ip consul):8500" \ --engine-opt="cluster-store=consul://$(docker-machine ip consul):8500" \
+--swarm-discovery="consul://$(docker-machine ip consul):8500" \
+--engine-opt="cluster-store=consul://$(docker-machine ip consul):8500" \
 --engine-opt="cluster-advertise=eth1:2376" \
 demo1
 ```
@@ -103,7 +104,7 @@ http {
 }
 ```
 
-Let's build and publish the image of this load-balancer to Docker Hub: 
+Let's build and publish the image of this load-balancer to Docker Hub:
 
 ```
 # Create image
@@ -160,7 +161,7 @@ networks:
     driver: overlay
 ```
 
-There are several important updates here  
+There are several important updates here
 * usage of the lb-dns image for the load balancer service
 * constraints to choose the nodes on which each service will run (needed in our example to illustrate the DNS round robin)
 * creation of a new user-defined overlay network to enable each container to communicate with each other through their name