Docker is becoming a popular technology for distributing and deploying web apps. It makes the whole development operations process easier, faster, and cheaper – all while reducing the number of servers needed. Why wouldn’t you want to use it?
I’m going to go through some of the most common Docker commands and what they do, then give some docker command examples so you can start experimenting with them right away.
Firstly, let’s get clear up some docker jargon terms to make sure you know what I’m talking about with each command:
- Container – These are are what docker is built on. They encapsulate an application and all of its libraries and dependencies, so it can be run anywhere Docker is installed.
- Image – A Docker Image is a file that is essentially a snapshot of a container. You can create a container by running a Docker Image
- Docker Hub – A public registry for developers to distribute their code.
- [OPTIONS] – Here’s where you can add options to your commands to get different results. Each command has lots of options associated with it. Refer to the documentation for all the details.
- [COMMAND] – Here’s where you put the parameters for your command. Depending on the command, it might be a file name or a container ID.
- [ARG…] – Here is where you can write additional arguments for a command
Docker Terminal Command Basics
Every docker command has a basic structure. Here’s an example docker command:
Important Docker Commands List
Here are some Docker commands to try out on the command line. Just make sure you have Docker running!
Description: docker run is probably the most important command on this Docker list. It creates a new container, then starts it using a specified command. It is the equivalent of using
docker create and then immediately using
docker start (we’ll go through those below).
docker run [OPTIONS] IMAGE [COMMAND] [ARG...]
docker run hello-world
This example will download, create and run the ‘hello-world’ container from docker hub. Try it out!
Description: This command creates a new container and prepares it to run the specified command, but doesn’t run it. The ID is printed to STDOUT. This command is similar to
docker run, but the container is never started. It can be started at any time with docker start <container_id>.
This can be useful if you want to create and prepare a container for running at a later time.
docker create [OPTIONS] IMAGE [COMMAND] [ARG...]
Download Our Project Specification Template
docker create hello-world
This will download and create the hello-world container same as above, but it won’t run it.
Description: Starts container, either created with
docker create or one that was stopped. More info
docker run [OPTIONS] IMAGE [COMMAND] [ARG...]
docker start hello-world
Description: Stops a running container. More info
docker stop [OPTIONS] CONTAINER [...]
docker start hello-world
This example will stop the container we started in the example above. You can use
docker start to start it back up again.
Description: Use this command to list the docker containers available. By default, only running ones are listed, but you can add options such as -a to get a docker container list. More info
docker ps [OPTIONS]
docker ps -a
The above command will display all containers on your system. The output will look something like this:
Description: Removes a container. Once you use
docker ps to list available containers, you can use this command to remove one or more of them.
docker rm [OPTIONS] CONTAINER [CONTAINER...]
docker rm -f redis
This example will remove the container called ‘redis’. The
-f tag forces the action, meaning the container will receive a
SIGKILL command first.
Description: rmi stands for remove image. Similar to
docker rm but removes the docker image rather than a running instance of an image (called a container).
docker rmi [OPTIONS] IMAGE [IMAGE...]
docker rmi test
This example will remove the image name ‘test’. Use the
docker images command to get a list of images and ids.
Read How We Helped a Marketing Company to Build a Back-Office Custom Ads Dashboard
Description: Let’s you login to a docker registry. You can use this command to log into any public or private registry. You’ll probably use this to log into Docker Hub.
docker login [OPTIONS] [SERVER]
docker login localhost:8080
Here we are logging into a self-hosted registry by specifying the server name. Otherwise, just use
docker login to login to your Docker Hub registry.
Description: Use this command to create a tag TARGET_IMAGE that refers to SOURCE_IMAGE.
docker tag SOURCE_IMAGE[:TAG] TARGET_IMAGE[:TAG]
docker tag 7d9495d03763 maryatdocker/docker-whale:latest
Here we are tagging a local image with ID “7d9495d03763″ into the “maryatdocker/docker-whale” repository with the tag “latest”
Description: docker push is the command you’ll use to share your images to Docker Hub or another registry. It’s a key part of the deployment process, and you’ll need to use it with
docker tag and
docker login to work properly.
docker push [OPTIONS] NAME[:TAG]
docker push maryatdocker/docker-whale
This example will push the image we tagged above to the repository. It’s actually the example from the docs, check out the full page here.
Cobine it with the tag command like this:
Description: The exec command can be used to run a command in a container that already running.
docker run lets us run a command when starting a container,
docker exec can be used to feed subsequent commands to a container.
docker exec [OPTIONS] CONTAINER COMMAND [ARG...]
First start a container with
docker run --name ubuntu_bash --rm -i -t ubuntu bash
Now we can execute a command on that container to create a new file with
docker exec -d ubuntu_bash touch /tmp/execWorks
Description: Getting deeper into using docker, the
docker logs command lets you see the log file for a running container. However, it can only be used with containers that were started with the
journald logging driver
docker logs [OPTIONS] CONTAINER
docker logs -f MyCntr
Description: Sometimes you just need to kill one or all running containers. Similar to
SIGKILL (this is actually the message it will receive),
docker kill will stop a container running.
docker kill [OPTIONS] CONTAINER [CONTAINER...]
docker kill MyCntr
docker swarm to manage a swarm. You can initialize a swarm, add manager and worker nodes, and update a swarm. This command is actually a whole bunch of commands in one – take a look at all of the child commands here.
docker swarm init --advertise-addr <MANAGER-IP>
This will initialize a swarm and give us back the address to add workers to the swarm later. For a better understanding of how to use docker swarms, take a look at the create a swarm tutorial on the docs.
This docker reference should be enough to get you started using docker on the command line. Signup for a Docker hub account if you don’t have one and have a go at deploying your own app. Once you get used to the process, you’ll never go back to your old deployment habits.
Try playing around to get used to how things work!