docker实战 代码勘误

Last updated August 21, 2016

In an effort to offer continued support beyond publication, we have listed many updates to code due to version updates.



[code - omission] Page 18



The command to start the "mailer" is missing a line. Where the book reads:

docker run -d \

  --name mailer \

the proper command should read:

docker run -d \

  --name mailer \

  dockerinaction/ch2_mailer

  

[code - regression] Page 68



Newer versions of Docker have changed the structure of the JSON returned by the docker inspect subcommand. If the following command does not work then use the replacement. Original:

docker inspect --format "{{json .Volumes}}" reader

Replacement:

docker inspect --format "{{json .Mounts}}" reader



[code - regression] Page 69



Newer versions of Docker have changed the structure of the JSON returned by the docker inspect subcommand. If the following command does not work then use the replacement. Original:

docker inspect --format "{{json .Volumes}}" student

Replacement:

docker inspect --format "{{json .Mounts}}" student



[code - regression] Page 74



The alpine image entrypoint has changed since original publication and has been unset. The last command on the page should now read:

docker run --rm \

  --volumes-from tools \

  --entrypoint /bin/sh \

  alpine:latest \

  -c 'ls /operations/*'

[code - regression] Page 75



The docker exec example on the top of page 75 was printed with the wrong tool name. The correct command is:

docker exec important_application /operations/tools/diagnostics



[code - regression] Page 86



It appears that nslookup behavior in the alpine image has changed. To run the example use the busybox:1 image.

docker run --rm \

  --hostname barker \

  busybox:1 \

  nslookup barker

  

[code - regression] Page 87 (top)



It appears that nslookup behavior in the alpine image has changed. To run the example use the busybox:1 image.

docker run --rm \

  --dns 8.8.8.8 \

  busybox:1 \

  nslookup docker.com

  

[code - regression] Page 87 (bottom)



It appears that nslookup behavior in the alpine image has changed. To run the example use the busybox:1 image.

docker run --rm \

  --dns-search docker.com \

  busybox:1 \

  nslookup registry.hub

  

[code - regression] Page 88 (bottom)



It appears that nslookup behavior in the alpine image has changed. To run the example use the busybox:1 image.

docker run --rm \

  --add-host test:10.10.10.255 \

  busybox:1 \

  nslookup test

  

[code - regression] Page 106



There are a few new problems with this example. First, the named repository (dockerfile/mariadb) no longer exists. You can use mariadb:5.5 as replacement. However, the second problem is that containers created from the mariadb image perform certain initialization at startup. That initialization work requires certain capabilities and to be started with the default user. The system should instead drop permissions after the initialization work is complete. Note that the real value of this example is in demonstrating different resource isolation mechanisms. It is not so important that you get it working. You can start the database with the following command:

docker run -d --name ch6_mariadb \

  --memory 256m \

  --cpu-shares 1024 \

  --cap-drop net_raw \

  -e MYSQL_ROOT_PASSWORD=test \

  mariadb:5.5

  

[code - regression] Page 107



Containers created from the wordpress:4.1 image perform certain initialization at startup and expect certain environment variables. That initialization work requires certain capabilities and to be started with the default user. The system should instead drop permissions after the initialization work is complete. Note that the real value of this example is in demonstrating different resource isolation mechanisms. It is not so important that you get it working. You can start wordpress with the following command:

docker run -d -P --name ch6_wordpress \

  --memory 512m \

  --cpu-shares 512 \

  --cap-drop net_raw \

  -e WORDPRESS_DB_PASSWORD=test \

  mariadb:5.5

  

[code - typo] Page 109



The device access example is missing the "run" subcommand. The command listed as:

docker -it --rm \

  --device /dev/video0:/dev/video0 \

  ubuntu:latest ls -al /dev

should have been written as:

docker run -it --rm \

  --device /dev/video0:/dev/video0 \

  ubuntu:latest ls -al /dev

  

[code - typo] Page 110 - 111



Several commands are missing the "run" subcommand. In each case the command begins with

docker -d ...

and should have been written as:

docker run -d ...



[code - regression] Page 115 (bottom)



The busybox and alpine images have been updated to fix the problem described in the paragraph below. The 'su' command does not have the SUID bit set and will not provide any automatic privilege escalation.



[command correction] Page 116



Boot2Docker has been discontinued and rolled into a newer project called Docker Machine. Because a reader is unlikely to have the boot2docker command installed, the command at the top of this page should be changed from:

boot2docker ssh

to the Docker Machine equivalent:

docker-machine ssh default

where default is the name of the machine you created.



[code - regression] Page 119



The ifconfig command has since been removed from ubuntu:latest. Instead of using the ubuntu:latest image for these examples use ubuntu:trusty. The example using ifconfig should look like:

docker run --rm \

  --privileged \

  ubuntu:trusty ifconfig

[Illustration Mistake] Page 136

Image layer ced2 on the left side of the illustration is listed at c3d2 on the right side. These two layers should represent the same item.



[code - typo] Page 140



Containers need not be in a running state in order to export their file system. The first command on page 140 uses the "run" subcommand but the command listed will never be able to start. Replace "run" with "create." The command should appear as follows:

docker create --name export-test \

  dockerinaction/ch7_packed:latest ./echo For Export

  

[code - missing line] Page 146



In the example Dockerfile near the top of the page the line with the RUN directive is missing part of the instruction. That line should read:

RUN apt-get update && apt-get install -y git



[code - evolution] Page 215



The registry:2 configuration file now requires the population of additional fields under "maintenance > uploadpurging." The example should currently look like:

# Filename: s3-config.yml

version: 0.1

log:

    level: debug

    fields:

        service: registry

        environment: development

storage:

    cache:

        layerinfo: inmemory

    s3:

        accesskey: 

        secretkey: 

        region: 

        bucket: 

        encrypt: true

        secure: true

        v4auth: true

        chunksize: 5242880

        rootdirectory: /s3/object/name/prefix

    maintenance:

        uploadpurging:

            enabled: true

            age: 168h

            interval: 24h

            dryrun: false

        readonly:

            enabled: false

http:

    addr: :5000

    secret: asecretforlocaldevelopment

    debug:

        addr: localhost:5001

        

[code - evolution] Page 216



The registry:2 configuration file now requires the population of additional fields under "maintenance > uploadpurging." The example should currently look like:

# Filename: rados-config.yml

version: 0.1

log:

    level: debug

    fields:

        service: registry

        environment: development

storage:

    cache:

        layerinfo: inmemory

    rados:

        poolname: radospool

        username: radosuser

        chunksize: 4194304

    maintenance:

        uploadpurging:

            enabled: false

            age: 168h

            interval: 24h

            dryrun: false

        readonly:

            enabled: false

http:

    addr: :5000

    secret: asecretforlocaldevelopment

    debug:

        addr: localhost:5001

        

[code - evolution] Page 218



The registry:2 configuration file now requires the population of additional fields under "maintenance > uploadpurging." The example should currently look like:

# Filename: redis-config.yml

version: 0.1

log:

    level: debug

    fields:

        service: registry

        environment: development

http:

    addr: :5000

    secret: asecretforlocaldevelopment

    debug:

        addr: localhost:5001

storage:

    cache:

        blobdescriptor: redis

    s3:

        accesskey: 

        secretkey: 

        region: 

        bucket: 

        encrypt: true

        secure: true

        v4auth: true

        chunksize: 5242880

        rootdirectory: /s3/object/name/prefix

    maintenance:

        uploadpurging:

            enabled: true

            age: 168h

            interval: 24h

            dryrun: false

        readonly:

            enabled: false

redis:

    addr: redis-host:6379

    password: asecret

    dialtimeout: 10ms

    readtimeout: 10ms

    writetimeout: 10ms

    pool:

        maxidle: 16

        maxactive: 64

        idletimeout: 300s

[code - typo] Page 220



The name of the file shown should be scalable-config.yml as in previous examples. This example also requires the addition of the newer uploadpurging attributes. The mainenance section of the file should be as follows:

    maintenance:

        uploadpurging:

            enabled: true

            age: 168h

            interval: 24h

            dryrun: false

        readonly:

            enabled: false

[text - typo] Page 240



In the second paragraph the reader is instructed to, "Open ./coffee/api/api.py" this is not the correct location of the file. The correct file location is at, "./coffee/app/api.py."

[text - typo] Page 262



The refere nce to "flock.json" in the first sentence of the third paragraph should be "flock.yml."

[code - typo] Page 270



The git clone command uses the ssh protocol instead of https. The command should read as follows:

git clone https://github.com/dockerinact ... i.git