The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
| Version |
Location |
Description |
Submitted by |
Date submitted |
|
Automated builds
ch 7 - topic - automated build. first Paragraph |
To try out automated build on Docker hub I forked from official code. Builds starts well but fails with following error:
Step 6 : COPY app /app
lstat app: no such file or directory
ERROR: Build failed: lstat app: no such file or directory
ERROR: Build failed with exit code 2
ERROR: Build in 'master:/identidock/Dockerfile' (68eb9269) failed in 0:02:59
|
Gaurav |
Apr 05, 2017 |
| ePub |
Chapter 4 Docker Fundamentals -> Managing Data with Volumes and Data Containers |
The command applies only if Linux is the host of the docker daemon.
"$ sudo touch /var/lib/docker/volumes/5cad.../_data/test-file"
If working through the book on macOS, the host of the docker daemon is actually a VM. To follow the examples listed on macOS, the command "screen ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/tty" needs to be ran to get into the shell of the VM. Then the code examples will look. This command is on macOS 64bit version 10.13.2 and Docker version: 17.09.1-ce
|
Darren Seet |
Jan 05, 2018 |
|
5
Chapter 5, "Hello World", 9th code block - using online version on safari.oreilly, so don't know page number |
Current code:
$ sed -i '' s/World/Docker/ app/identidock.py
$ curl localhost:5000
Hello Docker!
running this sed on ubuntu gives:
"sed: can't read s/World/Docker/: No such file or directory'
This code gives the expected results:
$ sed -i -e s/World/Docker/ app/identidock.py
|
Anonymous |
Jan 21, 2017 |
| Printed |
Page 144
1st CLI example |
Intro to example reads "Stop the old version and start the new:"
The shell command reads:
"$ docker-compose stop"
The subsequent output shows containers stopping, starting, being created and re-created. However, the starting/creating will not happen unless a subsequent docker-compose command is issued: and, importantly, using the 'prod.yml' file explicitly rather than the default 'docker-compose.yml'
A new line with the shell command:
"$ docker-compose -f prod.yml up -d"
needs to be inserted in the listing after the last "Stopping ... " line.
|
Anonymous |
Aug 11, 2017 |
| PDF, |
Page 206
3rd paragraph in Ambassadors section of chapter 11 |
They can can quickly become
should be
They can quickly become
|
Anonymous |
Aug 06, 2019 |