8. Managing Docker Containers with Kubernetes | Troubleshooting Docker

Sign In Start Free Trial

Book Overview & Buying
Table Of Contents
Feedback & Rating

Troubleshooting Docker

By : Navid Ahmed Shaikh, Vaibhav Kohli, Dua, John Wooten

1 (1)

Troubleshooting Docker

1 (1)

By: Navid Ahmed Shaikh, Vaibhav Kohli, Dua, John Wooten

Overview of this book

You?re pro Docker? You?ve read all about orchestration with Docker in books? Now learn how to troubleshoot Docker in practice. Gain all the tools to safely see Docker in action with this 2017 book.

Preface

Preface

What this book covers

What you need for this book

Who this book is for

Conventions

Reader feedback

Customer support

Free Chapter

1. Understanding Container Scenarios and an Overview of Docker

1. Understanding Container Scenarios and an Overview of Docker

Decoding containers

Unikernels

Summary

2. Docker Installation

2. Docker Installation

Installing Docker on Ubuntu

Installing Docker on Red Hat Linux

Deploy CentOS VM on AWS to run Docker containers

Installing Docker on CoreOS

Installing Docker on Fedora

Installing Docker with script

Installing Docker on SUSE Linux

Summary

3. Building Base and Layered Images

3. Building Base and Layered Images

Building container images

Image testing and debugging

Automated image building

Summary

4. Devising Microservices and N-Tier Applications

4. Devising Microservices and N-Tier Applications

Hype or hubris

Monolithic architecture

N-tier application architecture

Microservices architecture

Summary

5. Moving Around Containerized Applications

5. Moving Around Containerized Applications

Redistributing via Docker registry

Pushing images to Docker Hub

Docker Trusted Registry (DTR)

Docker Universal Control Plane

Summary

6. Making Containers Work

6. Making Containers Work

Privileged containers

Super-privileged container

Puppet

Ansible

Chef

Summary

7. Managing the Networking Stack of a Docker Container

7. Managing the Networking Stack of a Docker Container

Docker networking

docker0 bridge

Configuring DNS

Troubleshooting communication between containers and the external network

libnetwork and the Container Network Model

Docker networking tools based on overlay and underlay networks

Configuring an overlay network with the Docker Engine swarm node

Configuring OpenvSwitch (OVS) to work with Docker

Summary

8. Managing Docker Containers with Kubernetes

8. Managing Docker Containers with Kubernetes

Deploying Kubernetes on Bare Metal machine

Troubleshooting the Kubernetes Fedora manual setup

Deploying Kubernetes using Minikube

Deploying Kubernetes on AWS

Deploying Kubernetes on vSphere

Kubernetes setup troubleshooting

Kubernetes pod deployment

Deploying Kubernetes in a production environment

Debugging Kubernetes issues

Summary

9. Hooking Volume Baggage

9. Hooking Volume Baggage

Avoiding troubleshooting by understanding Docker volumes

Default case storing data inside the Docker container

Data-only container

Host mapped volume backed up by shared storage

Docker storage driver performance

Summary

10. Docker Deployment in a Public Cloud - AWS and Azure

10. Docker Deployment in a Public Cloud - AWS and Azure

Architecture of Amazon ECS

Troubleshooting - AWS ECS deployment

Updating Docker containers in the ECS cluster

Microsoft Azure container service architecture

Troubleshooting - The Microsoft Azure Container Service

Docker Beta for AWS and Azure

Summary

Customer Reviews

1 (1)

5 star

0%

4 star

0%

3 star

0%

2 star

0%

1 star

100%

Deploying Kubernetes in a production environment

In this section, we'll be covering some of the important points and concepts that can be used to deploy Kubernetes in production.

Exposing Kubernetes services: Once we deploy the Kubernetes pods, we expose them using services. The Kubernetes service is an abstraction, which defines a set of pods and a policy to expose them as a microservice. The service gets its own IP address, but the catch is that this address only exists within the Kubernetes cluster, which means the service is not exposed to the Internet. It's possible to expose the service directly on the host machine port, but once we expose the service on the host machine, we get into port conflicts. It also voids Kubernetes benefits and makes it harder to scale the deployed service:

Kubernetes service exposed through external load balancer
One solution is to add an external load balancer such as HAProxy or NGINX. This is configured with a backend for each Kubernetes service and proxies...

Visually different images

CONTINUE READING

83

Tech Concepts

36

Programming languages

73

Tech Tools

Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.

Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.

50+ new titles added per month and exclusive early access to books as they are being written.

Troubleshooting Docker

Search

Your notes and bookmarks