|
|
|
|
+++
|
|
|
|
|
title = "Mastering Docker - Russ McKendrick"
|
|
|
|
|
date = 2019-12-21
|
|
|
|
|
updated = 2021-02-12
|
|
|
|
|
|
|
|
|
|
[taxonomies]
|
|
|
|
|
tags = ["books", "reviews", "docker", "packt", "russ mckendrick", "it",
|
|
|
|
|
"stars:1", "published:2017"]
|
|
|
|
|
+++
|
|
|
|
|
|
|
|
|
|
[GoodReads Summary](https://www.goodreads.com/book/show/35820617-mastering-docker---second-edition):
|
|
|
|
|
Experience first- and third-party tools such as Docker Compose, Docker
|
|
|
|
|
Machine, Portainer, and Rancher Learn how to leverage Kubernetes, Amazon ECS,
|
|
|
|
|
and Docker Swarm and know when each solution is appropriate Discover how
|
|
|
|
|
Docker can be integrated into your daily workflows.
|
|
|
|
|
|
|
|
|
|
<!-- more -->
|
|
|
|
|
|
|
|
|
|
{{ stars(stars=1) }}
|
|
|
|
|
|
|
|
|
|
How does one "master" docker when there is not a single word about layers?
|
|
|
|
|
|
|
|
|
|
How does one "master" docker when you have "sudo apt update && sudo apt
|
|
|
|
|
install -y git" with a description of "so it doesn't have to wait for one
|
|
|
|
|
process to end to start the other"?
|
|
|
|
|
|
|
|
|
|
This is another book coming from a book farm where people write about things
|
|
|
|
|
they don't know properly. This is another book coming from a book farm where
|
|
|
|
|
reviewers seem picked in the basis of "does not know enough about the subject
|
|
|
|
|
to not make a fuss so we can publish it as soon as possible".
|
|
|
|
|
|
|
|
|
|
If you want to learn about docker, stay away from this book. It will do more
|
|
|
|
|
harm than good.
|
