Skip to content

Commit 7d6826f

Browse files
committed
cleaned up some chapter titles
1 parent 7fa55cd commit 7d6826f

6 files changed

Lines changed: 139 additions & 148 deletions

File tree

chapters/docker-basics.adoc

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -62,15 +62,15 @@ Once your Docker host has been created, it then has a number of commands for man
6262
. Upgrade Docker
6363
. Configure the Docker client to talk to a host
6464

65-
Docker Machine was already installed 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 Docker client.
65+
Docker Machine was already installed as part of Docker Toolbox during the setup.
6666

67-
Find out more about the details at the link:https://docs.docker.com/machine/[Docker Machine Website].
67+
Find out more details at link:https://docs.docker.com/machine/[Docker Machine Website].
6868

6969
Open Docker shell, check if docker machine is working:
7070

7171
docker-machine -v
7272

73-
It shows the output similar to the one shown below:
73+
It shows the output:
7474

7575
docker-machine version 0.5.0 (04cfa58)
7676

@@ -84,7 +84,7 @@ Check if your client is working using the following command:
8484

8585
docker -v
8686

87-
It shows the output similar to the following:
87+
It shows the output:
8888

8989
Docker version 1.9.0, build 76d6bc9
9090

@@ -141,4 +141,4 @@ PING dockerhost (192.168.99.101): 56 data bytes
141141
64 bytes from 192.168.99.101: icmp_seq=1 ttl=64 time=0.387 ms
142142
----
143143

144-
If it does, you're ready to start with the workshop.
144+
If it does, you're ready to start the workshop.

chapters/docker-container.adoc

Lines changed: 48 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
## Run Container
1+
## Run a Container
22

33
The first step in running any application on Docker is to run a container from an image. There are plenty of images available from the official Docker registry (aka 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.
44

@@ -200,8 +200,54 @@ Now we're ready to test http://dockerhost:8080 again. This works with the expose
200200
.Welcome WildFly
201201
image::plain-wildfly1.png[]
202202

203+
### Stop Container
204+
205+
. Stop a specific container:
206+
+
207+
[source, text]
208+
----
209+
docker stop <CONTAINER ID>
210+
----
211+
+
212+
. Stop all the running containers
213+
+
214+
[source, text]
215+
----
216+
docker stop $(docker ps -q)
217+
----
218+
+
219+
. Stop only the exited containers
220+
+
221+
[source, text]
222+
----
223+
docker ps -a -f "exited=-1"
224+
----
225+
226+
### Remove Container
227+
228+
. Remove a specific container:
229+
+
230+
[source, text]
231+
----
232+
docker rm 0bc123a8ece0
233+
----
234+
+
235+
. Remove containers meeting a regular expression
236+
+
237+
[source, text]
238+
----
239+
docker ps -a | grep wildfly | awk '{print $1}' | xargs docker rm
240+
----
241+
+
242+
. Remove all containers, without any criteria
243+
+
244+
[source, text]
245+
----
246+
docker rm $(docker ps -aq)
247+
----
248+
203249
[[Enabling_WildFly_Administration]]
204-
### Enabling WildFly Administration
250+
### Enable WildFly Administration
205251

206252
Default WildFly image exposes only port 8080 and thus is not available for administration using either the CLI or Admin Console. Lets expose the ports in different ways.
207253

@@ -294,51 +340,3 @@ In this case, Docker port mapping will be shown as:
294340
8080/tcp -> 0.0.0.0:8080
295341
9990/tcp -> 0.0.0.0:9990
296342
----
297-
298-
### Stop and Remove Container
299-
300-
#### Stop Container
301-
302-
. Stop a specific container:
303-
+
304-
[source, text]
305-
----
306-
docker stop <CONTAINER ID>
307-
----
308-
+
309-
. Stop all the running containers
310-
+
311-
[source, text]
312-
----
313-
docker stop $(docker ps -q)
314-
----
315-
+
316-
. Stop only the exited containers
317-
+
318-
[source, text]
319-
----
320-
docker ps -a -f "exited=-1"
321-
----
322-
323-
#### Remove Container
324-
325-
. Remove a specific container:
326-
+
327-
[source, text]
328-
----
329-
docker rm 0bc123a8ece0
330-
----
331-
+
332-
. Remove containers meeting a regular expression
333-
+
334-
[source, text]
335-
----
336-
docker ps -a | grep wildfly | awk '{print $1}' | xargs docker rm
337-
----
338-
+
339-
. Remove all containers, without any criteria
340-
+
341-
[source, text]
342-
----
343-
docker rm $(docker ps -aq)
344-
----

chapters/docker-image.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
== Docker Image
1+
== Build an Image
22

33
*PURPOSE*: This chapter explains how to create a Docker image.
44

chapters/docker-kubernetes.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
## Java Application on Kubernetes Cluster
1+
## Deploy Application on Kubernetes Cluster
22

33
[quote, github.com/GoogleCloudPlatform/kubernetes/]
44
Kubernetes is an open source system for managing containerized applications across multiple hosts, providing basic mechanisms for deployment, maintenance, and scaling of applications.

chapters/docker-swarm.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
[[Docker_Swarm]]
2-
## Java EE Application on Docker Swarm Cluster
2+
## Deploy Application on Docker Swarm Cluster
33

44
Docker Swarm is native clustering for Docker. It allows you create and access to a pool of Docker hosts using the full suite of Docker tools. Because Docker Swarm serves the standard Docker API, any tool that already communicates with a Docker daemon can use Swarm to transparently scale to multiple hosts
55

0 commit comments

Comments
 (0)