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.
| Version |
Location |
Description |
Submitted by |
Date submitted |
|
8-iv
Step 1 : Create a docker image for your app |
There seems to be a problem with the Dockerfile provided.
When I try to build a Docker image as specified in the book by running
sudo docker build -t perfuse/test .
I get the following error:
Step 4 : RUN apt-get install -y npm
---> Running in 62437ce301e2
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
npm : Depends: nodejs but it is not going to be installed
Depends: node-abbrev (>= 1.0.4) but it is not going to be installed
Depends: node-ansi (>= 0.3.0-2) but it is not going to be installed
Depends: node-ansi-color-table but it is not going to be installed
Depends: node-archy but it is not going to be installed
Depends: node-block-stream but it is not going to be installed
Depends: node-fstream (>= 0.1.22) but it is not going to be installed
Depends: node-fstream-ignore but it is not going to be installed
Depends: node-github-url-from-git but it is not going to be installed
Depends: node-glob (>= 3.1.21) but it is not going to be installed
Depends: node-graceful-fs (>= 2.0.0) but it is not going to be installed
Depends: node-inherits but it is not going to be installed
Depends: node-ini (>= 1.1.0) but it is not going to be installed
Depends: node-lockfile but it is not going to be installed
Depends: node-lru-cache (>= 2.3.0) but it is not going to be installed
Depends: node-minimatch (>= 0.2.11) but it is not going to be installed
Depends: node-mkdirp (>= 0.3.3) but it is not going to be installed
Depends: node-gyp (>= 0.10.9) but it is not going to be installed
Depends: node-nopt (>= 3.0.1) but it is not going to be installed
Depends: node-npmlog but it is not going to be installed
Depends: node-once but it is not going to be installed
Depends: node-osenv but it is not going to be installed
Depends: node-read but it is not going to be installed
Depends: node-read-package-json (>= 1.1.0) but it is not going to be inst
alled
Depends: node-request (>= 2.25.0) but it is not going to be installed
Depends: node-retry but it is not going to be installed
Depends: node-rimraf (>= 2.2.2) but it is not going to be installed
Depends: node-semver (>= 2.1.0) but it is not going to be installed
Depends: node-sha but it is not going to be installed
Depends: node-slide but it is not going to be installed
Depends: node-tar (>= 0.1.18) but it is not going to be installed
Depends: node-underscore but it is not going to be installed
Depends: node-which but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
time="2015-09-02T07:00:32Z" level=info msg="The command [/bin/sh -c apt-get i
nstall -y npm] returned a non-zero code: 100"
|
Femi Anthony |
Sep 02, 2015 |
| PDF |
Page 22
python ch1-1.py |
$ python ch1-1.py
the above line did not work as expected. what i did. create files 'client_secret.json' and 'sample.dat' in the same directory...
run command below
python ch1-1.py --noauth_local_webserver
for reasons I don't yet understand, authorization via the web was not successful, and so the round about way for authorization...
|
Anand Sandhinti |
Mar 30, 2018 |
| PDF |
Page 26
Last paragraph |
Github URL's and google link don't exist
|
Anonymous |
Aug 14, 2014 |
| ePub |
Page 49
United States |
The command being run and the discussion of the command don't match. --allow tcp:80 seems to be correct and --allowed=tcp:80 appears to be an error
Excerpt follows:
"test-vm$ gcloud compute firewall-rules create http --allow tcp:80
...
The --allowed=tcp:80 flag tells Compute Engine to allow all incoming connection requests via the TCP protocol and port 80 (the default port for HTTP/web service)."
|
geoffrey purdy |
Dec 30, 2014 |
| PDF |
Page 63
two step creation (step 1) |
$ gcloud compute disks create boot-disk --zone us-central1-a --image debian-7
The input for the 'image' variable is to be given in an uri format...
https://www.googleapis.com/compute/v1/projects/ubuntu-os-cloud/global/images/family/ubuntu-1404-lts
|
Anand Sandhinti |
Mar 30, 2018 |
| PDF |
Page 63
2nd step of 2 step process |
$ gcloud compute instances create test-vm-2 --zone us-central1-a \
--disk name=boot-disk boot=yes
Instead of space, there is to be a comma seperating name=boot-disk and boot=yes
$ gcloud compute instances create test-vm-2 --zone us-central1-a \
--disk name=boot-disk,boot=yes
similar error in page 62
|
Anand Sandhinti |
Mar 30, 2018 |
| PDF |
Page 65
end |
test-vm$ sudo /usr/share/google/safe_format_and_mount -m \
"mkfs.ext4 -F" /dev/sdb /mnt/pd0
command '/usr/share/google/safe_format_and_mount -m' is deprecated.
2 step process to format and mount
sudo mkfs.ext4 -F -E lazy_itable_init=0,lazy_journal_init=0,discard /dev/sdb
sudo mount -o discard,defaults /dev/sdb /mnt/pd0
for more details --> https://cloud.google.com/sdk/gcloud/reference/compute/disks/create
|
Anand Sandhinti |
Mar 30, 2018 |
| Printed |
Page 112
middle |
Some of the commands have been deprecated and need to be updated like this one:
gcloud compute instances create datastore-test --scopes compute-rw datastore userinfo-email
gcloud : WARNING: We noticed that you are using space-separated lists, which are deprecated. Please transition to using comma-separated lists instead (try "--scopes
compute-rw,datastore,userinfo-email"). If you intend to use [datastore, userinfo-email] as positional arguments, put the flags at the end.
At line:1 char:1
+ gcloud compute instances create datastore-test --scopes compute-rw datastore use ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (WARNING: We not...ags at the end.:String) [], RemoteException
|
jason.dinkel |
Jul 22, 2015 |
| PDF |
Page 129
end |
backend1$ sudo cp /tmp/index.html /var/www/index.html
backend1$ exit
sudo cp /tmp/index.html /var/www/index.html
The above line is refering to a different directory... the correct code should be
sudo cp /tmp/index.html /var/www/html/index.html
|
Anand Sandhinti |
Apr 04, 2018 |
| PDF |
Page 154
middle |
The code below is deprecated...
custom-image-reference$ sudo gcimagebundle \
-d /dev/sda -o /tmp/ --log_file=/tmp/image.log
use the below code to create custom image
gcloud compute images create custom-image-reference \
> --source-disk custom-image-reference \
> --source-disk-zone us-central1-a \
> --force
source: https://cloud.google.com/compute/docs/images/create-delete-deprecate-private-images
|
Anand Sandhinti |
Apr 05, 2018 |
| ePub |
Page 190
"Let’s now build a Docker image by running the following command:" |
When running the following command:
perfuse-dev$ sudo docker build -t perfuse/test . # Don't miss the dot!
... the user receives a set of errors culminating in:
E: Unable to correct problems, you have held broken packages.
time="2015-09-02T07:00:32Z" level=info msg="The command [/bin/sh -c apt-get install -y npm] returned a non-zero code: 100"
The fix is to change the Dockerfile. Look for the line:
RUN apt-get install -y npm
... and change it to:
RUN apt-get install -y nodejs
Further explanation can be found here: http://askubuntu.com/questions/462337/couldnt-install-npm-on-ubuntu
|
jeffrey eliasen |
Oct 05, 2015 |