Book Image

The Docker Workshop

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

The Docker Workshop

5 (2)
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

Working with the Splunk Query Language

The Splunk query language can be a little difficult to pick up, but once you do, you'll find it helpful to interpret, analyze, and present your data from your Splunk environment. The best way to get comfortable with the query language is to simply dive in.

The following list describes a few things to take into account when working with the query language:

  • Narrow your search: The larger the amount of data you want to search over, the longer your query will take to return a result. If you know the time frame or a source, such as the one we created for docker logs, the query will return the result faster.
  • Use simple search terms: If you have an idea of what will be included in your log (for example, ERROR or DEBUG), this is a great place to start with your search terms as it will also help limit the amount of data you are receiving. This is another reason why we used a tag in the previous section when adding logs to our Splunk...