In this chapter, we’ve seen why containers are called containers. We’ve also discussed how applications get easier to build, package, and run with the use of containers.

Containers

We discussed how applications were built before containers: most applications were running on a monolithic architecture. We also highlighted the demerits of monolithic architecture and how containers solved those issues:

Demerits of Monolithic Architecture	Merits of Containers
Applications took time to be built.	Applications are now built easily.
There were limitations in carrying out fixes or troubleshooting the application.	The images the applications are built into are lighter, which aid the scalability of the application easily.
There were issues with running applications on multiple environments.	With containerization, we can deploy and run applications on multiple and different environments.
Applications being deployed were really heavy, therefore, easily scaling those applications was difficult.	With the relationship between containers and microservices, applications can be decoupled and run on many containers while they interact via API connections. This aids in easy troubleshooting, version upgrade, and fixes on the application.

Getting Started

Introducing Troubleshooting Containers

Troubleshooting Docker

Fixing Common Issues with Docker

Resolving Docker Container Networking Errors

Troubleshooting Kubernetes

Troubleshooting Further in Kubernetes

Troubleshooting Docker Image Build Issues

Conclusion

Deploy a Full Stack Web Application over Kubernetes

Summary: Introduction to Troubleshooting Containers

Containers