Docker in Practice

As a web developer, I have little interest in using Docker directly. My interest is in using very poorly documented build interfaces to Docker such as Maven or Gradle. Aside from that, all I need are cheat sheets I can find anywhere online.

Great intro to the container technology.

Extremely good sets of tips for using docker. Really useful and pragmatic and addresses real world docker issues.

Easy to read and follow. I have a much better understanding of the internal working of Docker after reading this book.

There are by now quite a few introductory books on Docker, but they mostly suffer from the same faults: they cover only the simple things. Doing simple things with Docker is very simple, and hardly needs a book-length explanation, but as soon as you try to do something non-trivial with Docker, things get complicated very quickly. "Docker in Practice" is completely unafraid of this, and dives straight into solving real-world problems with containers: transitioning from VMs, breaking down a system into microservices, persisting volumes, advanced image building techniques, continuous integration and Selenium testing, etcd and confd, network simulation, security, monitoring, performance, and debugging.It also addresses what I think is the biggest issue with Docker in production today: configuration management and orchestration. Many people are still treating Docker as a 'lite' alternative to full-fat CM tools: Puppet, Chef, and so on, but they're in for an unpleasant surprise as the disease of 'container sprawl' sets in: fragile manual setups frozen as hard-to-maintain images, rapidly getting out of sync, with no central infrastructure-as-code repository, change control, or versioning. Full marks to the authors for tackling this head on, with detailed worked examples of managing Dockerfiles with traditional Unix tools such as Perl and make, Docker-native tools like Docker Compose, Helios, Swarm, and Kubernetes, and 'pure' CM tools such as Chef Solo.The Docker ecosystem is fluid and developing extremely fast; accordingly, the authors have wisely decided to make their survey of tools broad but shallow, giving just enough information in each recipe to get you up and running with a particular technique, but not so much detail that the book would rapidly become out of date. Finally, they are refreshingly honest about the bugs and shortcomings of Docker and associated tools, and provide practical advice and tips for actually getting stuff to work.For me, this is the one essential Docker book.

This book is a gem and it is a natural next step of journey of Docker understanding and its applications. I think we have a lot of into books on Docker, how to download it and install it. For anyone who is trying to actually use Docker on their production servers this simply is not enough. I am sure it is fun to play with Docker on local dev box, but how do you secure it and harden it when someone actually tries to break it? That's where this book comes in... it takes you to the next step and gives you fine details on how to make your Docker instance hacker proof (or at least try to prevent most common attacks :)). I would definitely recommend this book when you are comfortable with Docker in your dev environment and ready to productionalize it.

I haven't read all of this book and I suspect many won't at least to begin with. There are various different techniques here, some for example are about how to use Docker in production. I was more interested in the continuous integration stuff which was invaluable in me starting to get some different and useful automated testing of our software in my current position. Time will tell how much use the rest of my current team will gleam from this but I personally believe it could be pivotal to bringing our current release time periods down quite heavily.It's truly excellent to have examples of how to run services on docker in a VM like setting and then how to gradually move software into a microservices architecture, this is something we've been hoping to do for sometime but it's difficult with legacy code to truly catch all these things to the point where we sometimes don't even try. Having docker containers will force us to separate our architecture more and thus we should expect unit testing and the like to be much more effective. Also of a lot of use for me was how to share data so I can run tests checking SQLite database entries have changed within the container from HTTP requests coming from the outside and how to run commands on docker containers from the host and a large portion of Chapter 8 about running simulating real networks within docker.

I wish I could give this book 1,000 stars.. You have literally helped me in so many ways. These techniques are valuable and impart strategies that help me to save time and create different types of environments for Test, QA, and Prod. Ian, thank you and I would love to hear more of your knowledge and wisdom moving forward. Thank you for your contribution.

I wanted a book to learn the basics of Docker. This has been fantastic - really easy to read and with great examples. Highly recommended ..

A go-to Docker book! This book gives practical walkthroughs on how you can leverage Docker to create solutions. It’s well-structured and easy to follow. Recommended!

Il libro è molto dettagliato e chiaro.Probabilmente per chi non ne sa proprio nulla ci sono libri migliori.Tuttavia la parte iniziale fa un sufficiente tour di base attraverso le funzionalità del prodotto.Assolutamente da non perdere per chi è sistemista ed interessato alla gestione dei container.