Book Image

The Docker Workshop

By : Vincent Sesto, Onur Yılmaz, Sathsara Sarathchandra, Aric Renzo, Engy Fouda
5 (3)
Book Image

The Docker Workshop

5 (3)
By: Vincent Sesto, Onur Yılmaz, Sathsara Sarathchandra, Aric Renzo, Engy Fouda

Overview of this book

No doubt Docker Containers are the future of highly-scalable software systems and have cost and runtime efficient supporting infrastructure. But learning it might look complex as it comes with many technicalities. This is where The Docker Workshop will help you. Through this workshop, you’ll quickly learn how to work with containers and Docker with the help of practical activities.? The workshop starts with Docker containers, enabling you to understand how it works. You’ll run third party Docker images and also create your own images using Dockerfiles and multi-stage Dockerfiles. Next, you’ll create environments for Docker images, and expedite your deployment and testing process with Continuous Integration. Moving ahead, you’ll tap into interesting topics and learn how to implement production-ready environments using Docker Swarm. You’ll also apply best practices to secure Docker images and to ensure that production environments are running at maximum capacity. Towards the end, you’ll gather skills to successfully move Docker from development to testing, and then into production. While doing so, you’ll learn how to troubleshoot issues, clear up resource bottlenecks and optimize the performance of services. By the end of this workshop, you’ll be able to utilize Docker containers in real-world use cases.
Table of Contents (17 chapters)
Preface

Getting Container Logs into Splunk

Our log monitoring environment is starting to take shape, but we need to get our Docker container logs into the application to make it worth the work. We have set up our Splunk forwarder to send logs from our system to the /var/log directory. Up until now, we have learned that we can simply mount the log file of our container and use the Splunk forwarder to send logs to the Splunk indexer. This is one way to do this, but Docker provides an easier option for sending logs to Splunk.

Docker provides a log driver specific to Splunk that will send our container logs via our network to an HTTP Event Collector on our Splunk installation. We'll need to open a new port to expose the Event Collector as Splunk uses port 8088 to collect data in this method. So far, we've exposed ports 8000 and 9997 on our Splunk installation. Before we proceed with the rest of this chapter, let's look at all the available ports and how they function on Splunk...