To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzes reviews to verify trustworthiness.
Very dissapointed by structure and the organization of information in the book. If you want to start with Docker and dont have any experience with it, and you want to get understand the basics dont get fooled by the thickness and chapter names of the book. Author does not start from simple example, does not try to build on it, jumps from topic to another, and does not explain. For me this book is a dissapointment..
Please, don't get the headline wrong, this is not a bad book. It provides good coverage of Docker, but there are too many detailed examples that take away the real purpose of a Docker textbook, which should be teaching someone the philosophy and the design of Docker.
There are chapters on the design of Docker, but the chapters filled with many overly detailed examples tend to put themselves into the focus.
However, it seems that a book on Docker actually can't go too much into the above-described "grand" subjects. Why? Because Docker is largely made of smoke that hovers over the core elements provided by the Linux kernel, which are the control groups, namespaces and filesystems. The smoke is the DockerHub.
This is by no means a bad book. It just isn't what a textbook should be, but I've already described why.
Bought the book as I needed to Dockerize a JBoss WildFly and MongoDB application and deploy on AWS. In the end, I achieved this with the Docker Documentation and the help of Stack Overflow. Every time I hit a problem or wanted to understand something I tried to use the index and could never find what I was looking for. I appreciate that O'Reilly most probably has their own index creating software, but does a novice in the subject ever attempt to use the index prior to publication?
After a suggestion on 'Stack Overflow' the chapter (# 8) on 'Exploring Docker Compose' has proved useful. that's about it.
I bought this book as a reference guide, not a tutorial and I feel that the poor index makes it not very usable, until I have the time to read it cover to cover. Surprised it has got into a 2nd. edition as is - after reading (the small number of) very average reviews on USA site.
Well O'Reilly is the best as always except this book. If you need to Google commands like save a docker image or create a snapshot or roll back then why you bother paying 30 quid for this?
I think this book is awful I tried to make around it several times, but I just cannot. Also many pages about monitoring docker services. Great because first I would need to know the basics not the enterprise monitoring after 1/3 of the book. This is the best example how not to write a book.
If I need something that I don't know then again I had to Google it and end up on github or stackexchange or Ubuntu site to get the answer... Several free blog write ups are better than this book to be frank! Awful...
Nothing on building custom images. Almost nothing on Dockerfiles. Images come from .git repos, containers come from Docker registry. I would have expected to learn how to create my own images and deploy my own containers.
It's good: clear explanations, wide range of topics with information hard to find online. I only wished it was a bit more concise and focused since it's an "up and running" book. May be a "quick start" chapter including docker compose would have been good?