{"componentChunkName":"component---src-templates-blog-post-js","path":"/02-docker-learning-the-command-line/","result":{"data":{"site":{"siteMetadata":{"title":"Yamenai"}},"markdownRemark":{"id":"f83e3978-14b8-5aa6-9b7e-d6ea968e297e","excerpt":"Part 1: Digging into the Command Line Interface Introduction to Developing with Virtual Machines (VMs) and Docker Learning development on the JavaScript stack…","html":"

\n \n \n \n \n

\n

What is Docker

\n

Docker is a tool we can use to isolate and containerize our application and the environment in which it runs from that of our host machine. This allows us to also version our entire “stack” and all the requirements and dependencies for the application to run within version control.

\n

Why is Docker so great

\n

This is great for a plethora of reasons, but for me, the main advantage is how easily Docker can be run locally and deployed in production and help ensure that what works on my machine will work on every machine.

\n
\n

Note: I have run into instances where some of the terminal commands run to execute/build docker commands/images produce some errors when running on Windows, but with minor testing and tweaking, cross platform compatibility can be achieved.

\n
\n

What does Docker solve

\n

This eliminates the “well, it works on my machine” excuse from your vocabulary. This also helps ensure that any new developer who is on-boarded to your project, once they have git and docker installed, they’ll be ready to run your application.

\n
\n

For our demo, we will be aliasing npm commands to docker commands to make the development cycle more familiar to developers, and so, NPM is a dependency on the host machine, simply to kick start the docker commands.\nThese could also be aliased to bash commands but it would make the integration with CI tools, as we will see later, slightly different. Hence, I chose NPM.

\n
\n

Getting Started with the Command Line

\n

\"Fear

\n

Fear not the Terminal

\n

To get started with this demo, you should have Docker installed on your host machine.

\n
\n

This was written and performed on Mac. If you notice any commands that do not work for Windows, please leave a comment to help out other readers. I’ll try to update my notes here too.

\n
\n

Installing Docker

\n

A quick Google search for “install docker” eventually takes you here: https://docs.docker.com/install/\nThe installation steps have changed (in terms of where to find the download) a few times. I believe you will need to register for an account with Docker (and/or Docker Hub) but don’t worry, we’ll be using these later to publish our images to a Docker repository.

\n

Once you’ve completed the installation, join us back here and we’ll review a handful of commands we’ll be using over and over to make our lives easier.

\n
\n

Note: Terminology\nWe’ll be using terms like build, image and container a lot in this article, so I wanted to define them upfront.\nthe build is the process of taking the steps outlined in the Dockerfile (more on that later) to create your image.\nthe image is like an onion, built up in layers from your Dockerfile. This is your primary asset. Kind of like a class definition.\nthe container is an instance of your image. A container is to an image, like an object is to a class. You can have many containers of the same image if required.

\n
\n

Simple Commands

\n

So now docker is running. You can confirm this by running docker -v in your terminal. At the time of this article, I am using Docker version 18.09.0, build 4d60db4. You don’t need this version, but later in this series, I am planning to use some of the newer features. I’ll try to comment on those sections where a specific version (or newer) would be required.

\n

Running docker in your terminal will give you a long list of commands you can use to manage your Docker assets. Let’s look at a few:

\n

docker ps

\n
# Returns a list of running containers\n$ docker ps\nCONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
\n

Ok, so we see … nothing. But that’s because we have no containers running.. Let’s build our first image. For this we will pull a predefined image from docker’s repository. It’s time for hello-world!

\n

docker pull

\n
$ docker pull hello-world\nUsing default tag: latest\nlatest: Pulling from library/hello-world\nd1725b59e92d: Pull complete
\n

This command allows you to pull prebuilt images from repositories like Docker Hub. Let’s see all the repositories we have loaded on our machine.

\n

docker images

\n
$ docker images\nREPOSITORY                          TAG                 IMAGE ID            CREATED             SIZE\nhello-world                         latest              4ab4c602aa5e        3 months ago        1.84kB
\n

This shows us a list of built images that we have on our machines. You can easily bring up any of these in a container using the command we will look at next: docker run [IMAGE]:[TAG|'latest']

\n

docker run

\n
# This will pull, and run a container with the image provided\n$ docker run hello-world\n\nHello from Docker!\nThis message shows that your installation appears to be working correctly.\n...
\n

So what happened here? Basically, first docker looks at your local list of images. Since it didn’t find one tagged as hello-world it fell-back to docker hub and downloaded the image from that repo. Once it was pulled, Docker then created a container running this image.

\n

But if you read the output from our hello world, they already recommend what to try next.

\n
\n

To try something more ambitious, you can run an Ubuntu container with:
\n$ docker run -it ubuntu bash

\n
\n

Let’s see what happens.

\n
$ docker run -it ubuntu bash\nUnable to find image 'ubuntu:latest' locally\nlatest: Pulling from library/ubuntu\n32802c0cfa4d: Pull complete\nda1315cffa03: Pull complete\nfa83472a3562: Pull complete\nf85999a86bef: Pull complete\nDigest: sha256:6d0e0c26489e33f5a6f0020edface2727db9489744ecc9b4f50c7fa671f23c49\nStatus: Downloaded newer image for ubuntu:latest\nroot@3fab2218a261:/#
\n

Now we’re inside our Docker container! Crazy right? Try out some simple commands, muck around. Doesn’t matter.. We’ll review how to kill the container shortly. Right now, nothing inside your container is linked to your file system so anything you do in here will not be persisted.

\n

Go play! I’ll wait…

\n

Ok. So, before you $ exit your container, let’s open a new tab to see a little more of what’s going on. In your new container, let’s try our docker ps command again. You should see an entry like this:

\n
$ docker ps\nCONTAINER ID   IMAGE    COMMAND   CREATED              STATUS              PORTS       NAMES\n3fab2218a261   ubuntu   \"bash\"    About a minute ago   Up About a minute               elated_tesla
\n

We have 2 unique identifiers here that we should take note of, the CONTAINER ID and the NAME. This will allow us to get back into our container from another terminal window. We can try it by doing the next command we’ll review.

\n

docker exec

\n

With this docker command, we can execute a command against our running container, and we can even tell docker that we want to remain interactive -i and we want to open a terminal -t in our command. So, take the CONTAINER ID or the NAME from your docker ps command, and let’s get back into our running container with docker exec with out -it flag.

\n
$ docker exec -it elated_tesla bash\nroot@3fab2218a261:/#
\n

And we’re right back in the terminal of our container! Pretty cool, eh? Ok, let’s start cleaning up. Let’s simply exit out of the container in our second terminal window with just $ exit

\n

Now, let’s see the command we would use to stop our container if we weren’t logged into the terminal. This is how you will be stopping containers that are running in detached -d mode.

\n

docker stop

\n
$ docker stop elated_tesla\nelated_tesla
\n

Now, if we run docker ps again, we’ll see an empty list. Well, that is a little misleading. Since Docker isn’t persisting to our host machine, it didn’t just kill off everything we’ve done. The container still exists, but we can’t see it. Let’s add a flag to our docker ps command.

\n
$ docker ps -a\nCONTAINER ID        IMAGE                          COMMAND                  CREATED             STATUS                        PORTS                  NAMES\n3fab2218a261        ubuntu                         \"bash\"                   10 minutes ago      Exited (0) 43 seconds ago                            elated_tesla\n6088b6cbbab0        hello-world                    \"/hello\"                 13 minutes ago      Exited (0) 13 minutes ago                            upbeat_robinson
\n

Found em! The problem is, they’re still consuming some (not much, but some) resources. Let’s full clear them out. Keep in mind that anything you did inside of the container really will be lost once we fully remove the container. But in this case, that is fully ok. We want a fresh start.

\n

docker rm

\n
$ docker rm elated_tesla\nelated_tesla
\n

Now, when we run docker ps -a again, we’ll see this has been removed from our list of stopped containers. However, if we run docker images we will see that ubuntu is still an image we have on our host machine. This just means when we spin up a new container, we won’t need to download anything from Docker Hub (unless we use a different tag than the one we have locally)

\n
\n

Although we won’t got into it in this article, if system resources ever become an issue, you can run docker image prune or docker container prune to free up some resources.

\n
\n

Recap

\n

Ok! So, we covered off how to pull images, turn them into containers, start and stop, remove and execute against them. We’re at a pretty good place, we can start to look at building our own custom Docker images! Stay tuned for part 2 where we’ll dockerize a simple Vuejs app!

\n

Please, feel free to do your happy dance in the meantime ;)

\n

\"Happy

","frontmatter":{"title":"Docker for Frontend Devs - Learning the Command Line Interface","date":"February 12, 2019","description":"Learn the Docker CLI (Command Line Interface) to get comfortable managing images, and containers, and understand what Docker is, why we use it and the problems it aims to solve. Using the CLI you'll pull Docker images, create and destroy containers and mount volumes and network interfaces."}}},"pageContext":{"slug":"/02-docker-learning-the-command-line/","previous":{"fields":{"slug":"/01-writing-custom-tslint-rule-from-scratch/"},"frontmatter":{"title":"Writing a Custom TSLint Rule From Scratch"}},"next":{"fields":{"slug":"/03-docker-creating-custom-docker-images/"},"frontmatter":{"title":"Docker for Frontend Devs - Custom Docker Images for Development"}}}},"staticQueryHashes":["240262808","2841359383"]}