Sunday, November 22, 2026
TR
Linux

How to Install and Use Docker Compose on Ubuntu 20.04

How to Install and Use Docker Compose on Ubuntu 20.04
Contents
  1. Step 1 — Installing Docker Compose
  2. docker-compose.ymlStep 2 — Setting Up the File
  3. Step 3 — Running Docker Compose
  4. Step 4 — Getting Familiar with Docker Compose Commands

Step 1 — Installing Docker Compose

To make sure you get the most up-to-date stable version of Docker Compose, you will download this software from its official GitHub repository .

First, confirm the latest version available on the releases page . At the time of writing, the most current stable version is 1.29.2.

The following command will download the 1.29.2 release and save the executable file at /usr/local/bin/docker-compose, which will make this software globally accessible as docker-compose:

Next, set the correct permissions so that the docker-compose command is executable:

sudo chmod +x /usr/local/bin/docker-compose
sudo curl -L "https://github.com/docker/compose/releases/download/1.29.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose

To verify that the installation was successful, you can run:

docker-compose --version

You will see output similar to this:

Outputdocker-compose version 1.29.2, build 5becea4c

Docker Compose is now successfully installed on your system. In the next section, you will see how to set up a docker-compose.yml file and how to bring up a containerized environment with this tool.

docker-compose.ymlStep 2 — Setting Up the File

To demonstrate how to set up a docker-compose.yml file and work with Docker Compose, you will create a web server environment using the official Nginx image from Docker Hub, the public Docker registry. This containerized environment will serve a single static HTML file.

Begin by creating a new directory in your home folder, and then moving into it:

mkdir ~/compose-demo
cd ~/compose-demo

In this directory, set up an application folder that will serve as the document root for your Nginx environment:

mkdir app

Using your preferred text editor, create a new index.html file inside the app folder:

nano app/index.html

Place the following content in this file: ~/compose-demo/app/index.html

<!doctype html>
<html lang="en">
<head>
    <meta charset="utf-8">
    <title>Docker Compose Demo</title>
    <link rel="stylesheet" href="https://cdn.jsdelivr.net/gh/kognise/water.css@latest/dist/dark.min.css">
</head>
<body>

    <h1>This is a Docker Compose Demo Page.</h1>
    <p>This content is being served by an Nginx container.</p>

</body>
</html>

When you are done, save and close the file. If you are using nano, you can do this by typing CTRL+X Y ENTER to confirm.

Next, create the docker-compose.yml file:

nano docker-compose.yml

Add the following content to your docker-compose.yml file: docker-compose.yml

version: '3.7'
services:
  web:
    image: nginx:alpine
    ports:
      - "8000:80"
    volumes:
      - ./app:/usr/share/nginx/html

The docker-compose.yml file typically starts with a version definition. This tells Docker Compose which configuration version you are using.

Next you have the services block, where you set up the services that are part of this environment. In your case, you have a single service named web. This service uses the nginx:alpine image and sets up a port redirection with the ports directive. All requests on port Host 8000 of the host machine (the system from which you are running Docker Compose) will be redirected to the container on port 80, where Nginx will be running (web80).

The volumes directive will create a shared volume between the host machine and the container. This will share the local appfolder with the container, and the volume will be located inside the container at /usr/share/nginx/html, which will then overwrite the default document root for Nginx.

Save and close the file.

You have set up a demo page and a docker-compose.yml file to create a containerized web server environment that will serve it. In the next step, you will bring up this environment with Docker Compose.

Step 3 — Running Docker Compose

With the docker-compose.yml file in place, you can now run Docker Compose to bring up your environment. The following command will download the necessary Docker images, create a container for the webservice, and run the containerized environment in background mode:

docker-compose up -d

Docker Compose will first look for the defined image on your local system, and if it cannot find it, it will download the image from Docker Hub. You will see output like this:

OutputCreating network "compose-demo_default" with the default driver
Pulling web (nginx:alpine)...
alpine: Pulling from library/nginx
cbdbe7a5bc2a: Pull complete
10c113fb0c77: Pull complete
9ba64393807b: Pull complete
c829a9c40ab2: Pull complete
61d685417b2f: Pull complete
Digest: sha256:57254039c6313fe8c53f1acbf15657ec9616a813397b74b063e32443427c5502
Status: Downloaded newer image for nginx:alpine
Creating compose-demo_web_1 ... done

Your environment is now up and running in the background. To verify that the container is active, you can run:

docker-compose ps

This command will show you information about the running containers and their state, as well as any port redirections currently in place:

Output       Name                     Command               State          Ports        
----------------------------------------------------------------------------------
compose-demo_web_1   /docker-entrypoint.sh ngin ...   Up      0.0.0.0:8000->80/tcp

You can now access the demo application by pointing your browser to localhost:8000 if you are running this demo on your local machine, or your_server_domain_or_IP:8000 if you are running it on a remote server.

You will see a page like this:

The shared volume you set up in the docker-compose.yml file keeps your app folder files in sync with the container's document root. If you make any changes to the index.htmlfile, they will be picked up automatically by the container and thus reflected in your browser when you reload the page.

In the next step, you will see how to manage your containerized environment with Docker Compose commands.

Step 4 — Getting Familiar with Docker Compose Commands

You have seen how to set up a docker-compose.yml file and bring up your environment with docker-compose up. Now you will see how to use Docker Compose commands to manage and interact with your containerized environment.

To check the logs produced by your Nginx container, you can use the logscommand:

docker-compose logs

You will see output similar to this:

OutputAttaching to compose-demo_web_1
web_1  | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
web_1  | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
web_1  | /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
web_1  | 10-listen-on-ipv6-by-default.sh: Getting the checksum of /etc/nginx/conf.d/default.conf
web_1  | 10-listen-on-ipv6-by-default.sh: Enabled listen on IPv6 in /etc/nginx/conf.d/default.conf
web_1  | /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
web_1  | /docker-entrypoint.sh: Configuration complete; ready for start up
web_1  | 172.22.0.1 - - [02/Jun/2020:10:47:13 +0000] "GET / HTTP/1.1" 200 353 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.61 Safari/537.36" "-"

If you want to pause the environment's execution without changing the current state of your containers, you can use:

docker-compose pause
OutputPausing compose-demo_web_1 ... done

To resume execution after issuing a pause:

docker-compose unpause
OutputUnpausing compose-demo_web_1 ... done

The stop command will terminate container execution, but it will not destroy any data associated with your containers:

docker-compose stop
OutputStopping compose-demo_web_1 ... done

If you want to remove the containers, networks and volumes associated with this containerized environment, use the down command:

docker-compose down
OutputRemoving compose-demo_web_1 ... done
Removing network compose-demo_default

Note that this will not remove the base image used by Docker Compose to spin up your environment (in your case, nginx:alpine). That way, whenever you bring your environment up again with a docker-compose up, the process will be much faster because the image is already on your system.

If you also want to remove the base image from your system, you can use:

docker image rm nginx:alpine
OutputUntagged: nginx:alpine
Untagged: nginx@sha256:b89a6ccbda39576ad23fd079978c967cecc6b170db6e7ff8a769bf2259a71912
Deleted: sha256:7d0cdcc60a96a5124763fddf5d534d058ad7d0d8d4c3b8be2aefedf4267d0270
Deleted: sha256:05a0eaca15d731e0029a7604ef54f0dda3b736d4e987e6ac87b91ac7aac03ab1
Deleted: sha256:c6bbc4bdac396583641cb44cd35126b2c195be8fe1ac5e6c577c14752bbe9157
Deleted: sha256:35789b1e1a362b0da8392ca7d5759ef08b9a6b7141cc1521570f984dc7905eb6
Deleted: sha256:a3efaa65ec344c882fe5d543a392a54c4ceacd1efd91662d06964211b1be4c08
Deleted: sha256:3e207b409db364b595ba862cdc12be96dcdad8e36c59a03b7b3b61c946a5741a

Kerim Koç

Systems and infrastructure engineer. I write about Linux, open source, high availability and security.