Host management
by Scott Gallagher, Allan Espinosa, Russ McKendrick, Santosh Kumar Konduri, Vaibhav
Docker: Creating Structured Containers
- Docker
- Table of Contents
- Docker
- Meet Your Course Guide
- 1. Course Module 1: Learning Docker
- 1. Getting Started with Docker
- An introduction to Docker
- Docker on Linux
- Differentiating between containerization and virtualization
- Docker networking/linking
- Installing Docker
- Downloading the first Docker image
- Running the first Docker container
- Running a Docker container on Amazon Web Services
- Troubleshooting
- 2. Up and Running
- Docker terminologies
- Docker commands
- The daemon command
- The version command
- The info command
- The run command
- The search command
- The pull command
- The start command
- The stop command
- The restart command
- The rm command
- The ps command
- The logs command
- The inspect command
- The top command
- The attach command
- The kill command
- The cp command
- The port command
- Running your own project
- Dockerfile
- 3. Container Image Storage
- 4. Working with Docker containers and images
- 5. Publishing Images
- 6. Running Your Private Docker Infrastructure
- 7. Running Services in a Container
- 8. Sharing Data with Containers
- 9. Docker Machine
- 10. Docker Compose
- 11. Docker Swarm
- 12. Testing with Docker
- 13. Debugging Containers
- 1. Getting Started with Docker
- 2. Course Module 2: Networking Docker
- 1. Docker Networking Primer
- 2. Docker Networking Internals
- 3. Building Your First Docker Network
- 4. Networking in a Docker Cluster
- 5. Next Generation Networking Stack for Docker – libnetwork
- 3. Course Module 3: Monitoring Docker
- 1. Introduction to Docker Monitoring
- 2. Using the Built-in Tools
- 3. Advanced Container Resource Analysis
- 4. A Traditional Approach to Monitoring Containers
- 5. Querying with Sysdig
- 6. Exploring Third Party Options
- 7. Collecting Application Logs from within the Container
- 8. What Are the Next Steps?
- 4. Course Module 4: Securing Docker
- 1. Securing Docker Hosts
- 2. Securing Docker Components
- 3. Securing and Hardening Linux Kernels
- 4. Docker Bench for Security
- Docker security – best practices
- Docker – best practices
- CIS guide
- The Docker Bench Security application
- Running the tool
- Understanding the output
- Understanding the output – host configuration
- Understanding the output – the Docker daemon configuration
- Understanding the output – the Docker daemon configuration files
- Understanding the output – container images and build files
- Understanding the output – container runtime
- Understanding the output – Docker security operations
- 5. Monitoring and Reporting Docker Security Incidents
- 6. Using Docker's Built-in Security Features
- 7. Securing Docker with Third-Party Tools
- 8. Keeping up Security
- 5. Course Module 5: Mastering Docker
- 1. Docker in Production
- 2. Shipyard
- 3. Panamax
- 4. Tutum
- 5. Advanced Docker
- A. Reflect and Test Yourself! Answers
- Module 1: Learning Docker
- Chapter 1: Getting Started with Docker
- Chapter 6: Running Your Private Docker Infrastructure
- Chapter 7: Running Services In a Container
- Chapter 8: Sharing Data with Containers
- Chapter 9: Docker Machine
- Chapter 10: Orchestrating Docker
- Chapter 11: Docker Swarm
- Chapter 12: Testing with Docker
- Chapter 13: Debugging Containers
- Module 2: Networking Docker
- Module 3: Monitoring Docker
- Module 4: Securing Docker
- Chapter 2: Securing Docker Components
- Chapter 3: Securing and Hardening Linux Kernels
- Chapter 4, Docker Bench for Security
- Chapter 5, Monitoring and Reporting Docker Security Incidents
- Chapter 6, Using Docker's Built-in Security Features
- Chapter 7, Securing Docker with Third-party Tools
- Chapter 8, Keeping up Security
- Module 5: Mastering Docker
- Module 1: Learning Docker
- B. Bibliography
- Index
In this section, we will focus on host management, that is, the ways we can manage our hosts, what we should use to manage our hosts, how we can monitor our hosts, and container failover, which is very important when something happens to the host that is running critical containers.
With host monitoring you can do so via the command line using Docker Machine as also there are some GUI applications out there that can be useful as well. For Machine, you can use the ls subcommand:
$ docker-machine ls NAME ACTIVE DRIVER STATE URL SWARM amazonhost amazonec2 Error swarm-master * virtualbox Running tcp://192.168.99.102:2376 swarm-master(master) swarm-node1 virtualbox Running tcp://192.168.99.103:2376 swarm-master
You can use some GUI applications out there as well, such as:
- Shipyard: https://shipyard-project.com/
- DockerUI: https://github.com/crosbymichael/dockerui
- Panamax: http://panamax.io/
Another tool that you can use for node management is that of Docker Swarm. We saw previously how helpful Swarm can be. Remember that you can use Docker Swarm to manage your hosts as well as to create and list them. The most useful command to remember for Swarm is the list subcommand. With the list subcommand, you can get a view of all the nodes and their statuses:
Remember that you will need either the discovery service IP or the token number that is used for Swarm:
$ docker run swarm list token://<swarm_token>
With Docker Swarm, you can set up your manager node to be highly available. That is, if the managing host dies, you can have it failover to another host. If you don't have it set up, there will be a service interruption, as you won't be able to communicate to your hosts anymore and will need to reset them up to point to the new Docker Swarm manager. You can set up as many replicas as you want.
To set this up, you will need to use the --replication and --advertise flags. This tells Swarm that there will be other managers for failover. It will also tell Swarm what address to advertise on, so the other managers know on what IP address to connect for other Swarm managers.
-
No Comment