anchor.diff:  You used Docker Machine already during the attendee setup. We won't need it too much further on. But if you need to create hosts, it's a very handy tool to know about. From now on we're mostly going to use the docker client.
   Find out more about the details at the link:https://docs.docker.com/machine/[Official Docker Machine Website]
   
  -Check if docker machine is working with
  +Check if docker machine is working using the following command:
   
   [source, text]
   ----
  
positive.code: meida
  ----
  
  If you have noticed the startup log of the server, you should have discovered that the server is located in the /opt/jboss/wildfly and that by default the public interfaces are bound to the 0.0.0.0 address whilst the admin interfaces are bound just to localhost. This information will be useful to learn how to customize the server.
  
  So, in order to access to our wildfly server, we need to know which address has been chosen by the application server for socket binding. We will use the docker inspect command passing as parameter the ID of the running Container we have already found (48f473979e50):
  
  [source, text]
  ----
  docker inspect --format "{{.NetworkSettings.IPAddress}}" 48f473979e50
  ----
  
  The above command outputs an IP address (maybe 172.17.0.1)
  That means, the server is available at the 172.17.0.1 IP Address.
  Now let's open the console at that address: http://172.17.0.1:8080
  
  That did not work. You'll get a "This webpage is not available - ERR_CONNECTION_TIMED_OUT" error. But why? Docker runs containers in the host, who is running in a guest system.
  
  When Docker starts, it creates a virtual interface named docker0 on the host machine. It randomly chooses an address and subnet from the private range defined by RFC 1918 that are not in use on the host machine, and assigns it to docker0. Docker made the choice 172.17.0.1 in this example.
  But docker0 is no ordinary interface. It is a virtual Ethernet bridge that automatically forwards packets between any other network interfaces that are attached to it. This lets containers communicate both with the host machine and with each other. But nothing more.
  Speaking, by default Docker containers can make connections to the outside world, but the outside world cannot connect to containers.
  This get's another layer of indirection, if you are using boot2docker on for example Mac or Windows. In this case, we don't even care for the Docker generated IP address, but want to know the address, the host is running at.
  
  We did find it out earlier with `docker-machine ip` which gave us the host IP address. We added it to the hosts file. So, we can give it another try by accessing: http://dockerhost:8080
  This will not work either. If you want containers to accept incoming connections, you will need to provide special options when invoking `docker run`.
  The container, we just started, can't be accessed by our browser. We need to stop it again and restart with different options.
  
  [source, text]
  ----
  
negative.code: docker run -it <INSTRUCTOR_IP>:5000/wildfly
  ----
  
  Seems the server started correctly. We can check it by issuing the `docker ps` command which retrieves the images process which are running and the ports engaged by the process:
  
  [source, text]
  ----
  docker ps
  