Fix #14 - Include Kubernetes, Remove Swarm, Update to Docker 1.9

Author: rafabene

attendees/docker-compose-internet.yml

@@ -1,12 +1,12 @@
 mysqldb:
-  image: classroom.example.com:5000/mysql
+  image: mysql
   environment:
     MYSQL_DATABASE: sample
     MYSQL_USER: mysql
     MYSQL_PASSWORD: mysql
     MYSQL_ROOT_PASSWORD: supersecret
 mywildfly:
-  image: classroom.example.com:5000/wildfly-mysql-javaee7
+  image: arungupta/wildfly-mysql-javaee7
   links:
     - mysqldb:db
   ports:

chapters/docker-basics.adoc

@@ -52,7 +52,7 @@ These instructions are stored in a file called a Dockerfile. Docker reads this D
 
 A container consists of an operating system, user-added files, and meta-data. As we've seen, each container is built from an image. That image tells Docker what the container holds, what process to run when the container is launched, and a variety of other configuration data. The Docker image is read-only. When Docker runs a container from an image, it adds a read-write layer on top of the image (using a union file system as we saw earlier) in which your application can then run.
 
-### Docker Machine
+### Docker Machine (For Windows and Mac)
 
 Machine makes it really easy to create Docker hosts on your computer, on cloud providers and inside your own data center. It creates servers, installs Docker on them, then configures the Docker client to talk to them.
 
@@ -72,7 +72,7 @@ Check if docker machine is working:
 
 It shows the output similar to the one shown below:
 
-  docker-machine version 0.4.1 (e2c88d6)
+  docker-machine version 0.5.0 (04cfa58)
 
 NOTE: The exact version may differ based upon how recently the installation was performed.
 
@@ -86,7 +86,7 @@ Check if your client is working using the following command:
 
 It shows the output similar to the following:
 
-  Docker version 1.8.2, build 0a8c2e3
+  Docker version 1.9.0, build 76d6bc9
 
 NOTE: The exact version may differ based upon how recently the installation was performed.
 

chapters/docker-compose.adoc

@@ -28,12 +28,12 @@ An application using Docker containers will typically consist of multiple contai
 
 NOTE: According to https://docs.docker.com/compose/install/ "You can run Compose on OS X and 64-bit Linux. It is currently not supported on the Windows operating system."
 
-### Install docker compose
+### Install docker compose (For Linux users)
 
 [source, txt]
 ----
-curl -L https://github.com/docker/compose/releases/download/1.4.2/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
-chmod +x /usr/local/bin/docker-compose
+sudo curl -L https://github.com/docker/compose/releases/download/1.5.0/docker-compose-`uname -s`-`uname -m` -o /usr/local/bin/docker-compose
+sudo chmod +x /usr/local/bin/docker-compose
 ----
 
 ### Configuration File
@@ -43,21 +43,27 @@ chmod +x /usr/local/bin/docker-compose
 [source, yml]
 ----
 mysqldb:
-  image: [classroom.example.com:5000/]mysql
+  #From Internet
+  image: mysql
+  #From Instructor
+  image: classroom.example.com:5000/mysql
   environment:
     MYSQL_DATABASE: sample
     MYSQL_USER: mysql
     MYSQL_PASSWORD: mysql
     MYSQL_ROOT_PASSWORD: supersecret
 mywildfly:
-  image: [classroom.example.com:5000|arungupta]/wildfly-mysql-javaee7
+  #From Internet
+  image: arungupta/wildfly-mysql-javaee7
+  #From Instructor
+  image: classroom.example.com:5000/wildfly-mysql-javaee7
   links:
     - mysqldb:db
   ports:
     - 8080
 ----
 +
-This file is available in https://raw.githubusercontent.com/redhat-developer/docker-java/javaone2015/attendees/[] and shows:
+This file is available in https://raw.githubusercontent.com/redhat-developer/docker-java/devoxxma2015/attendees/[] and shows:
 +
 .. Two services defined by the name `mysqldb` and `mywildfly`
 .. Image name for each service defined using `image`

chapters/docker-container.adoc

@@ -47,7 +47,7 @@ We call the union of the read-write layer and all the read-only layers a _union
 image::images/plain-wildfly0.png[]
 ====
 
-In our particular case, the https://github.com/jboss-dockerfiles/wildfly/blob/9.0.1.Final/Dockerfile[jboss/wildfly] image extends the https://github.com/jboss-dockerfiles/base-jdk/blob/jdk8/Dockerfile[jboss/base-jdk:8] image which adds the OpenJDK distribution on top of the https://github.com/jboss-dockerfiles/base/blob/master/Dockerfile[jboss/base] image.
+In our particular case, the https://github.com/jboss-dockerfiles/wildfly/blob/9.0.2.Final/Dockerfile[jboss/wildfly] image extends the https://github.com/jboss-dockerfiles/base-jdk/blob/jdk8/Dockerfile[jboss/base-jdk:8] image which adds the OpenJDK distribution on top of the https://github.com/jboss-dockerfiles/base/blob/master/Dockerfile[jboss/base] image.
 The base image is used for all JBoss community images. It provides a base layer that includes:
 
 . A jboss user (uid/gid 1000) with home directory set to `/opt/jboss`
@@ -65,7 +65,6 @@ When the download is done, you can list the images again and will see the follow
 docker images
 REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
 jboss/wildfly       latest              7688aaf382ab        6 weeks ago         581.4 MB
-swarm               latest              207e8b983242        9 weeks ago         10.2 MB
 ----
 
 ### Run Container
@@ -104,7 +103,7 @@ This will show the output as:
 OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
 17:02:58,000 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final
 17:02:58,251 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
-17:02:58,311 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting
+17:02:58,311 INFO  [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final) starting
 17:02:59,558 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 11) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 17:02:59,560 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 3) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
 ...
@@ -114,7 +113,7 @@ OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was
 17:03:00,891 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/jboss/wildfly/standalone/deployments
 17:03:01,131 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
 17:03:01,133 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
-17:03:01,138 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started in 3431ms - Started 203 of 379 services (210 services are lazy, passive or on-demand)
+17:03:01,138 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final) started in 3431ms - Started 203 of 379 services (210 services are lazy, passive or on-demand)
 ----
 
 This shows that the server started correctly, congratulations!

chapters/docker-deployment-options.adoc

@@ -88,9 +88,9 @@ image::images/jbds1.png[]
 .WildFly Runtime Properties
 image::images/jbds2.png[]
 +
-. If a new runtime needs to be created, pick the directory for WildFly 9.0.1:
+. If a new runtime needs to be created, pick the directory for WildFly 9.0.2:
 +
-.WildFly 9.0.1.Final Runtime
+.WildFly 9.0.2.Final Runtime
 image::images/jbds3.png[]
 +
 Click on '`Finish`'.
@@ -141,7 +141,7 @@ TThe Command Line Interface (CLI) is a tool for connecting to WildFly instances
 
 Lets use the CLI to deploy javaee7-simple-sample to WildFly running in the container.
 
-. CLI needs to be locally installed and comes as part of WildFly. This should be available in the previously downloaded WildFly. Unzip into a folder of your choice (e.g. `/Users/<USER>/tools/`). This will create `wildfly-9.0.0.Final` directory here. This folder is referred to $WIDLFY_HOME from here on. Make sure to add the `/Users/<USER>/tools/wildfly-9.0.0.Final/bin` to your $PATH.
+. CLI needs to be locally installed and comes as part of WildFly. This should be available in the previously downloaded WildFly. Unzip into a folder of your choice (e.g. `/Users/<USER>/tools/`). This will create `wildfly-9.0.2.Final` directory here. This folder is referred to $WIDLFY_HOME from here on. Make sure to add the `/Users/<USER>/tools/wildfly-9.0.2.Final/bin` to your $PATH.
 +
 . Run the "`wildfly-management`" image with fixed port mapping as explained in <<Management_Fixed_Port_Mapping>>.
 . Run the `jboss-cli` command and connect to the WildFly instance.
@@ -240,7 +240,7 @@ docker run -d --name wildfly -p 8080:8080 -p 9990:9990 classroom.example.com:500
 +
 In addition to application port 8080, the administration port 9990 is exposed as well. The WildFly image that is used has tweaked the start script such that the management interface is bound to 0.0.0.0.
 +
-. Create a new server adapter in JBoss Developer Studio and name it "`WildFly 9.0.0-Management`". Specify the host name as '`dockerhost`'.
+. Create a new server adapter in JBoss Developer Studio and name it "`WildFly 9.0.2-Management`". Specify the host name as '`dockerhost`'.
 +
 image::images/jbds8.png[]
 +

chapters/docker-image.adoc

@@ -28,149 +28,97 @@ _Dockerfile_ is usually called _Dockerfile_. The complete list of commands that
 
 . Create a new directory.
 . Create a new text file, name it _Dockerfile_, and use the following contents:
-+
+
 [source, text]
 ----
-FROM ubuntu
+#From Internet
+FROM fedora
+
+#From Instructor
+FROM classroom.example.com:5000/fedora
 
 CMD ["/bin/echo", "hello world"]
 ----
-+
-This image uses `ubuntu` as the base image. `CMD` command defines the command that needs to run. It provides a different entry point of `/bin/echo` and gives the argument "`hello world`".
-+
+
+This image uses `fedora` as the base image. `CMD` command defines the command that needs to run. It provides a different entry point of `/bin/echo` and gives the argument "`hello world`".
+
 . Build this image:
-+
+
 ```console
 > docker build -t helloworld .
 Sending build context to Docker daemon 2.048 kB
-Step 0 : FROM ubuntu
-Pulling repository docker.io/library/ubuntu
-a5a467fddcb8: Download complete 
-3fd0c2ae8ed2: Download complete 
-9e19ac89d27c: Download complete 
-ac65c371c3a5: Download complete 
-Status: Downloaded newer image for ubuntu:latest
- ---> a5a467fddcb8
-Step 1 : CMD /bin/echo hello world
- ---> Running in 132bb0bf823f
- ---> e81a394f71e3
-Removing intermediate container 132bb0bf823f
-Successfully built e81a394f71e3
+Step 1 : FROM fedora
+latest: Pulling from library/fedora
+369aca82a5c0: Pull complete
+a887c7ad7f3f: Pull complete
+Digest: sha256:a220110e096cd1d6034699a5e30a012de6c55c83149d01658120918d01f1587a
+Status: Downloaded newer image for fedora:latest
+ ---> a887c7ad7f3f
+Step 2 : CMD /bin/echo hello world
+ ---> Running in 47e65a18749c
+ ---> 405849ed68f1
+Removing intermediate container 47e65a18749c
+Successfully built 405849ed68f1
 ```
-+
+
 `.` in this command is the context for `docker build`.
-+
+
 . List the images available:
-+
+
 ```console
 > docker images
 REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
-helloworld          latest              9c0e7b56cbee        13 minutes ago      187.9 MB
+helloworld          latest              405849ed68f1        18 seconds ago      204.3 MB
+fedora              latest              a887c7ad7f3f        6 days ago          204.3 MB
 ```
-+
+
 . Run the container:
-+
+
   docker run -it helloworld
-+
+
 to see the output:
-+
+
   hello world
-+
-. Change the base image from `ubuntu` to `busybox` in `Dockerfile`. Build the image again:
-+
+
+. Change the base image from `fedora` to `busybox` in `Dockerfile`. Build the image again:
+
   docker build -t helloworld2 .
-+
+
 and view the images as:
-+
+
 ```console
 > docker images
-REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
-helloworld          latest              e81a394f71e3        26 minutes ago      187.9 MB
-helloworld2         latest              c458787fadcf        3 seconds ago       1.113 MB
-ubuntu              latest              a5a467fddcb8        2 days ago          187.9 MB
-busybox             latest              3d5bcd78e074        4 days ago          1.113 MB
+REPOSITORY          TAG                 IMAGE ID            CREATED              VIRTUAL SIZE
+helloworld2         latest              3dece940fa4a        6 seconds ago        1.109 MB
+helloworld          latest              405849ed68f1        About a minute ago   204.3 MB
+fedora              latest              a887c7ad7f3f        6 days ago           204.3 MB
+busybox             latest              c51f86c28340        8 days ago           1.109 MB
 ```
 
 === WildFly Image
 
 . Create a new directory.
 . Create a new text file, name it _Dockerfile_, and use the following contents:
-+
+
 [source, text]
 ----
+#From Internet
 FROM jboss/wildfly
-----
-+
-. Build the image:
-+
-  docker build -t mywildfly .
-+
-. Run the container:
-+
-  docker run -it mywildfly
 
-=== Java EE 7 Application Image
-
-. Create a new directory.
-. Create a new text file, name it _Dockerfile_, and use the following contents:
-+
-[source, text]
+#From Instructor
+FROM classroom.example.com:5000/wildfly
 ----
-FROM jboss/wildfly <1>
-
-CMD ["/opt/jboss/wildfly/bin/standalone.sh", "-c", "standalone-full.xml", "-b", "0.0.0.0"] <2>
 
-RUN curl -L https://github.com/javaee-samples/javaee7-hol/raw/master/solution/movieplex7-1.0-SNAPSHOT.war -o /opt/jboss/wildfly/standalone/deployments/movieplex7-1.0-SNAPSHOT.war <3>
-----
-+
-Three things in this image:
-+
-<1> Uses "`jboss/wildfly`" as the base image
-<2> Starts WildFly application server in Full Platform mode
-<3> Copies the WAR file from from a URL to the deployment directory of WildFly
-+
 . Build the image:
 
-  docker build -t movieplex .
-
-=== Dockerfile Command Design Patterns
-
-==== Difference between CMD and ENTRYPOINT
-
-*TL;DR* `CMD` will work for most of the cases.
-
-Default entry point for a container is `/bin/sh`, the default shell.
-
-Running a container as `docker run -it ubuntu` uses that command and starts the default shell. The output is shown as:
-
-```console
-> docker run -it ubuntu
-root@88976ddee107:/#
-```
-
-`ENTRYPOINT` allows to override the entry point to some other command, and even customize it. For example, a container can be started as:
-
-```console
-> docker run -it --entrypoint=/bin/cat ubuntu /etc/passwd
-root:x:0:0:root:/root:/bin/bash
-daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
-bin:x:2:2:bin:/bin:/usr/sbin/nologin
-sys:x:3:3:sys:/dev:/usr/sbin/nologin
-. . .
-```
-
-This command overrides the entry point to the container to `/bin/cat`. The argument(s) passed to the CLI are used by the entry point.
-
-==== Difference between ADD and COPY
+  docker build -t mywildfly .
 
-*TL;DR* `COPY` will work for most of the cases.
+. Run the container:
 
-`ADD` has all capabilities of `COPY` and has the following additional features:
+  docker run -it mywildfly
 
-. Allows tar file auto-extraction in the image, for example, `ADD app.tar.gz /opt/var/myapp`.
-. Allows files to be downloaded from a remote URL. However, the downloaded files will become part of the image. This causes the image size to bloat. So its recommended to use `curl` or `wget` to download the archive explicitly, extract, and remove the archive.
 
-==== Import and export images
+=== Import and export images
 
 Docker images can be saved using `save` command to a .tar file: