anchor.diff:  
   The first step in running any application on Docker is to run an image. There are plenty of images available from the official Docker registry (aka link:https://hub.docker.com[Docker Hub]). To run any of them, you just have to ask the Docker Client to run it. The client will check if the image already exists on Docker Host. If it exists then it'll run it, otherwise the host will download the image and then run it.
   
  -### Pull the WildFly Image
  +### Pull Image
   
   Let's first check, if there are any images already available:
   
  
positive.code: <INSTRUCTOR_IP>:5000/wildfly  latest  2ac466861ca1   10 weeks ago  951.3 MB
  ----
  
  ### Run the WildFly Container
  
  #### Run Interactive Container
  
  Run WildFly container in an interactive mode.
  
  
negative.code: 
  Also try `docker ps -a` to see all the containers on this machine.
  
  ### Run Container with Default Port
  
  Startup log of the server shows that the server is located in the `/opt/jboss/wildfly`. It also shows that the public interfaces are bound to the `0.0.0.0` address while the admin interfaces are bound just to `localhost`. This information will be useful to learn how to customize the server.
  
  `docker-machine ip <machine-name>` gives us the Docker Host IP address and this was already added to the hosts file. So, we can give it another try by accessing: http://dockerhost:8080. However, 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.
  
  