- Use promo code GIFTBOOK18 to save $5.00 when you spend $20.00 or more on Books shipped and sold by Amazon.com. Enter code GIFTBOOK18 at checkout. Here's how (restrictions apply)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Docker in Practice 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
There is a newer edition of this item:
Frequently bought together
Customers who bought this item also bought
Special offers and product promotions
About the Author
Ian Miell is an experienced software engineer who first recognized the potential of Docker in his company and created his own tool in the Docker ecosystem.
Aidan Hobson Sayers has a strong interest in the practical detail and often dives into the Docker source code.
Showing 1-8 of 12 reviews
There was a problem filtering reviews right now. Please try again later.
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.
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.