The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".
The following errata were submitted by our customers and approved as valid errors by the author or editor.
Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
| Version |
Location |
Description |
Submitted By |
Date submitted |
Date corrected |
|
chapter 3 |
In chapter 3 of a digital version.
$ docker-machine stop local
And then you can run this to restart it (you need it to be running):
$ docker-machine start local
{
Stopping "local"...
Machine "local" was stopped.
}
The text between the curly brackets should be after the previous command "$ docker-machine stop local" and not where it is now.
Note from the Author or Editor:
This errata is actually from the second release of the first edition. This is fixed in the second edition and later. |
Charbel Khawand |
Dec 09, 2021 |
Mar 22, 2019 |
| Printed, |
Page 24
1st paragraph |
systems -> system
"One is used to track the filesystem layers that comprise images, and the other is a tagging systems for images."
should read
"One is used to track the filesystem layers that comprise images, and the other is a tagging system for images."
Note from the Author or Editor:
Fix already commited |
Alfred Myers |
Dec 17, 2019 |
Feb 07, 2020 |
| Printed, |
Page 50-54
code snipet and text |
Revision 9e5c122 of https://github.com/spkane/docker-node-hello updated the node version which has effects on pages 50-54.
On page 50 where read:
"FROM node:0.10"
should read:
"FROM node:11.11.0"
On page 51 where read:
"node:0.10.33. The base image that follows will provide you with an Ubuntu Linux image running Node 0.10.x."
should read:
"node:11.11.0. The base image that follows will provide you with an Ubuntu Linux image running Node 11.11.0."
On the last paragraph of page 54 where read:
"0.10"
should be read:
"11.11.0"
Note from the Author or Editor:
already fixed |
Alfred Myers |
Jan 13, 2020 |
Feb 07, 2020 |
| Printed, |
Page 51
4th paragraph |
In
"In the following code, you’ll use a collection of RUN instructions to start and create the required file structure that you need, and install some required software dependencies. You’ll also start to use the build variables you defined in the previous section to save you a bit of work and help protect you from typos.
RUN apt-get -y update
# The daemons
RUN apt-get -y install supervisor
RUN mkdir -p /var/log/supervisor"
build variables aren't used until the next code snippet, so
"You’ll also start to use the build variables you defined in the previous section to save you a bit of work and help protect you from typos"
should be moved close to the corresponding code snippet
Note from the Author or Editor:
Fix submitted |
Alfred Myers |
Jan 13, 2020 |
Feb 07, 2020 |
|
Page 79
2nd paragraph |
"of the / operator" should read "of the \ operator" (backslash needed for line continuation, not forward slash; typo)
Note from the Author or Editor:
Confirmed. Committing a fix. |
Anonymous |
Jul 23, 2022 |
|
|
Page 100
1st paragraph |
The statement "Setting the --memory-swap option to -1 will disable swap completely within the container" is incorrect (or outdated).
According to the docker docs (section "memory swap details"), explicitly setting --memory-swap to -1 allows the container to use unlimited swap.
Note from the Author or Editor:
This is an error that also exists in the 3rd edition. I am committing a fix now. |
Dominik Gresch |
Sep 12, 2022 |
|
| Printed |
Page 131
Warning |
"logging friver" should be "logging driver"
|
JP Vossen |
Jan 09, 2019 |
Mar 22, 2019 |
|
Page 135
Last paragraph of "Block I/O" chapter |
"In our experience, the --device-read-ops and --device-write-ops are the most effective way to set limits,"
Which one is meant here? Either -iops or -bps could be possible because both commands (--device-read-ops, --device-write-ops) are not valid and either have to end with -iops or -bps instead of -ops.
Note from the Author or Editor:
It should have read:
"In our experience, the --device-read-iops and --device-write-iops are the most effective way to set limits,"
This is being updated. Thank you for submitting the errata! |
Christopher Graf |
Nov 14, 2021 |
|
| Printed |
Page 158
tip |
"not grown into" should be "not grow into"
|
JP Vossen |
Jan 09, 2019 |
Mar 22, 2019 |