anchor.diff:  
   REPOSITORY              TAG     IMAGE ID       CREATED       VIRTUAL SIZE
   <INSTRUCTOR_IP>:5000/wildfly  latest  2ac466861ca1   10 weeks ago  951.3 MB
  -
  -----
  -
  -Run WildFly in the container:
  +----
  +
  +### Run the WildFly Container
  +
  +#### Run Interactively
  +
  +Run WildFly container in an interactive mode.
  +
   [source, text]
   ----
   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:
  +This will show the output as:
  +
  +[source, text]
  +----
  +> docker run -it 192.168.99.100:5000/wildfly
  +=========================================================================
  +
  +  JBoss Bootstrap Environment
  +
  +  JBOSS_HOME: /opt/jboss/wildfly
  +
  +  JAVA: /usr/lib/jvm/java/bin/java
  +
  +  JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
  +
  +=========================================================================
  +
  +17:58:58,353 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
  +17:58:58,891 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
  +17:58:59,056 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015899: WildFly 8.2.0.Final "Tweek" starting
  +
  +. . .
  +
  +17:59:03,211 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
  +17:59:03,212 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
  +17:59:03,213 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 5310ms - Started 184 of 234 services (82 services are lazy, passive or on-demand)
  +----
  +
  +This shows that the server started correctly, congratulations!
  +
  +Hit Ctrl+C to stop the container.
  +
  +#### Run as a Daemon
  +
  +Restart the container in a daemon mode:
  +
  +[source, text]
  +----
  +> docker run -d 192.168.99.100:5000/wildfly
  +972f51cc8422eec0a7ea9a804a55a2827b5537c00a6bfd45f8646cb764bc002a
  +----
  +
  +The output is the unique id assigned to the container. Check the logs as:
  +
  +[source, text]
  +----
  +> docker logs 972f51cc8422eec0a7ea9a804a55a2827b5537c00a6bfd45f8646cb764bc002a
  +=========================================================================
  +
  +  JBoss Bootstrap Environment
  +
  +  JBOSS_HOME: /opt/jboss/wildfly
  +
  +. . .
  +----
  +
  +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]
   ----
  
positive.code: docker images
  ----
  
  At first, this list ist empty. Now, let's get a plain `jboss/wildfly` image from your instructor's registry:
  
  [source, text]
  ----
  docker pull <INSTRUCTOR_IP>:5000/wildfly
  ----
  
  Typically, you'll 
  
  You can see, that Docker is downloading the immage with it's different layers.
  In a traditional Linux boot, the kernel first mounts the root File System as read-only, checks its integrity, and then switches the whole rootfs volume to read-write mode.
  When Docker mounts the rootfs, it starts read-only, as in a traditional Linux boot, but then, instead of changing the file system to read-write mode, it takes advantage of a union mount to add a read-write file system over the read-only file system. In fact there may be multiple read-only file systems stacked on top of each other. We think of each one of these file systems as a layer.
  At first, the top read-write layer has nothing in it, but any time a process creates a file, this happens in the top layer. And if something needs to update an existing file in a lower layer, then the file gets copied to the upper layer and changes go into the copy. The version of the file on the lower layer cannot be seen by the applications anymore, but it is there, unchanged.
  We call the union of the read-write layer and all the read-only layers a union file system.
  
  .Docker Layers
  image::images/plain-wildfly0.png[]
  
negative.code: 
  https://github.com/arun-gupta/docker-java/tree/master/attendees[Download and setup attendee laptop].
  
  ## Docker Basics
  Docker simplifies software delivery by making it easy to build and share images that contain your application’s entire environment, or application operating system.
  
  **What does it mean by application operating system ?**
  