Book Image

Mastering Docker, Fourth Edition - Fourth Edition

Book Image

Mastering Docker, Fourth Edition - Fourth Edition

Overview of this book

Docker has been a game changer when it comes to how modern applications are deployed and created. It has now grown into a key driver of innovation beyond system administration, with a significant impact on the world of web development. Mastering Docker shows you how you can ensure that you're keeping up with the innovations it's driving and be sure you're using it to its full potential. This fourth edition not only demonstrates how to use Docker more effectively but also helps you rethink and reimagine what you can achieve with it. You'll start by building, managing, and storing images along with exploring best practices for working with Docker confidently. Once you've got to grips with Docker security, the book covers essential concepts for extending and integrating Docker in new and innovative ways. You'll also learn how to take control of your containers efficiently using Docker Compose, Docker Swarm, and Kubernetes. By the end of this Docker book, you’ll have a broad yet detailed sense of what's possible with Docker and how seamlessly it fits in with a range of other platforms and tools.
Table of Contents (22 chapters)
1
Section 1: Getting Up and Running with Docker
8
Section 2: Clusters and Clouds
16
Section 3: Best Practices

Using Kubernetes and Docker Desktop

Now that we have our Kubernetes cluster up and running on our Docker desktop installation, we can start to interact with it. To start with, we are going to look at the command line that was installed alongside the Docker desktop component, kubectl.

As mentioned, kubectl was installed alongside Docker. The following command will show some information about the client and also the cluster it is connected to:

$ kubectl version

Like when running docker version, this should give you information on both the client and server:

Figure 11.7 – Checking the versions of the client and server

Next, we can run the following to see if kubectl can see our node:

$ kubectl get nodes

As we only have a single node, we should only see one listed:


Figure 11.8 – Listing our nodes

Now that we have our client interacting with our node, we can view the namespaces that are configured by...