Book Image

Docker on Amazon Web Services

By : Justin Menga
Book Image

Docker on Amazon Web Services

By: Justin Menga

Overview of this book

Over the last few years, Docker has been the gold standard for building and distributing container applications. Amazon Web Services (AWS) is a leader in public cloud computing, and was the first to offer a managed container platform in the form of the Elastic Container Service (ECS). Docker on Amazon Web Services starts with the basics of containers, Docker, and AWS, before teaching you how to install Docker on your local machine and establish access to your AWS account. You'll then dig deeper into the ECS, a native container management platform provided by AWS that simplifies management and operation of your Docker clusters and applications for no additional cost. Once you have got to grips with the basics, you'll solve key operational challenges, including secrets management and auto-scaling your infrastructure and applications. You'll explore alternative strategies for deploying and running your Docker applications on AWS, including Fargate and ECS Service Discovery, Elastic Beanstalk, Docker Swarm and Elastic Kubernetes Service (EKS). In addition to this, there will be a strong focus on adopting an Infrastructure as Code (IaC) approach using AWS CloudFormation. By the end of this book, you'll not only understand how to run Docker on AWS, but also be able to build real-world, secure, and scalable container platforms in the cloud.
Table of Contents (26 chapters)
Title Page
Copyright and Credits
Dedication
Packt Upsell
Contributors
Preface
Index

Questions


  1. True/false: You use the FROM and TO directives to define a multi-stage Dockerfile.
  2. True/false: The docker command --rm flag automatically deletes a container after it has exited.

 

  1. True/false: When you run your workflow, you should only build application artifacts once.
  2. True/false: When running the docker-compose run command with no additional flags, if the targeted services started fails with an error, docker-compose will exit with a non-zero code.
  3. True/false: When running the docker-compose up command with no additional flags, if one of the services started fails with an error, docker-compose will exit with a non-zero code.
  4. True/false: You should configure a Docker Compose version of 3.x if you want to use Docker Swarm.
  5. You configure the service_healthy condition on a dependency of a service in your Docker file.  Then you run the service using the docker-compose run command; the dependency is started, however, Docker Compose does not wait until the dependency is healthy and starts...