EN

Applications

Install Docker Engine and Docker Compose

Install Docker Engine and Docker Compose from the official repository on Debian or Ubuntu: users, logs, ports, updates, backups and best practices.

6 min read, updated on 18 November 2026

On this page

This guide explains how to install Docker Engine and the Docker Compose plugin from Docker's official repository, then how to prepare your server for production use: user permissions, log rotation, port exposure, updates and backups.

Order a Server

To host your containers, HostMyServers offers several options:

Prerequisites

  • A 64-bit server running Debian 12/13 or Ubuntu 22.04/24.04
  • SSH access with root or a sudo user

Ports: Docker does not need any incoming port. Only open the ports of the applications you publish, and never expose the Docker API (2375 or 2376) to the Internet: accessing it is equivalent to controlling the server.

Step 1: remove conflicting packages

Docker packages provided by the distribution can conflict with the official packages:

Terminal
sudo apt update
sudo apt remove $(dpkg --get-selections docker.io docker-compose docker-compose-v2 docker-doc docker-buildx podman-docker containerd runc 2>/dev/null | cut -f1)

Any images and volumes in /var/lib/docker are not deleted by this command.

Step 2: add the official repository

These commands work for both Debian and Ubuntu, because they read the system from /etc/os-release:

Terminal
sudo apt install ca-certificates curl
sudo install -m 0755 -d /etc/apt/keyrings
. /etc/os-release
sudo curl -fsSL "https://download.docker.com/linux/$ID/gpg" -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc

sudo tee /etc/apt/sources.list.d/docker.sources > /dev/null <<EOF
Types: deb
URIs: https://download.docker.com/linux/$ID
Suites: ${UBUNTU_CODENAME:-$VERSION_CODENAME}
Components: stable
Architectures: $(dpkg --print-architecture)
Signed-By: /etc/apt/keyrings/docker.asc
EOF

sudo apt update

Step 3: install Docker

Terminal
sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
sudo systemctl enable --now docker containerd

Step 4: verify the installation

Terminal
sudo systemctl status docker
docker --version
docker compose version
sudo docker run --rm hello-world

The message Hello from Docker! confirms that the engine can download an image and start a container.

Step 5: allow a user

To run Docker without sudo, add your user to the docker group, then log out and log back in:

Terminal
sudo usermod -aG docker $USER

Then check:

Terminal
docker run --rm hello-world

Step 6: configure logs and the daemon

By default, the json-file driver does not limit the size of logs, which can end up filling the disk. Create /etc/docker/daemon.json:

Terminal
sudo nano /etc/docker/daemon.json
JSON
{
  "log-driver": "local",
  "log-opts": {
    "max-size": "10m",
    "max-file": "3"
  },
  "live-restore": true
}
Option Effect
log-driver: local Compact log format, with rotation
max-size, max-file Up to 3 files of 10 MB per container
live-restore Containers keep running if the daemon stops

Validate the file, then restart Docker. This restart interrupts running containers: preferably do it before deploying your applications.

Terminal
sudo dockerd --validate --config-file=/etc/docker/daemon.json
sudo systemctl restart docker
docker info --format '{{.LoggingDriver}} {{.LiveRestoreEnabled}}'

The log driver only applies to new containers. Recreate existing containers to benefit from it, for example with docker compose up -d --force-recreate.

Step 7: control published ports

If a reverse proxy runs on the server, publish your applications on the local address only:

YAML
ports:
  - "127.0.0.1:8080:80"

You can also make the local address the default behavior by adding these keys to /etc/docker/daemon.json:

JSON
{
  "ip": "127.0.0.1",
  "default-network-opts": {
    "bridge": {
      "com.docker.network.bridge.host_binding_ipv4": "127.0.0.1"
    }
  }
}

Merge them with the file from step 6, validate it, then restart Docker. A port meant to be public will then have to be specified explicitly, for example "0.0.0.0:443:443".

Step 8: start a first Compose project

Create a folder for the project:

Terminal
sudo mkdir -p /opt/myapp
sudo chown "$USER": /opt/myapp
cd /opt/myapp
nano compose.yaml
YAML
services:
  web:
    image: nginx:1.30-alpine
    restart: unless-stopped
    ports:
      - "127.0.0.1:8080:80"
    volumes:
      - web-data:/usr/share/nginx/html
    healthcheck:
      test: ["CMD", "wget", "-qO-", "http://127.0.0.1/"]
      interval: 30s
      timeout: 5s
      retries: 3

volumes:
  web-data:

Start, then check:

Terminal
docker compose config --quiet
docker compose up -d
docker compose ps
docker compose logs --tail=20 web
curl -I http://127.0.0.1:8080

To publish this application over HTTPS, place a reverse proxy in front of it. You can start from the guide Install Nginx and PHP-FPM and the Let's Encrypt guide.

Useful commands

Command Description
docker ps -a List containers
docker compose logs -f Follow the project logs
docker compose restart Restart the services
docker compose down Stop and remove containers, keeping volumes
docker system df Show disk space used

Updates

Docker Engine

Terminal
sudo apt update
sudo apt install --only-upgrade docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin
docker --version

live-restore only covers patch updates. For a major version, plan for an interruption of your containers and read Docker's release notes.

Application images

Change the tag in compose.yaml if you pin it, then:

Terminal
cd /opt/myapp
docker compose pull
docker compose up -d
docker image prune

Backup

At a minimum, back up your Compose files, your .env files and your volumes. Volumes are located in /var/lib/docker/volumes, but it is better to archive them through a temporary container. The actual volume name is obtained with docker volume ls:

Terminal
cd /opt/myapp
mkdir -p backups
docker compose stop web
docker run --rm -v myapp_web-data:/data:ro -v "$PWD/backups":/backup alpine:3 tar czf /backup/web-data.tar.gz -C /data .
docker compose start web

To restore the archive into a volume:

Terminal
docker compose stop web
docker run --rm -v myapp_web-data:/data -v "$PWD/backups":/backup:ro alpine:3 tar xzf /backup/web-data.tar.gz -C /data
docker compose start web

For a database, prefer an export with the engine's own tool (mariadb-dump, pg_dump, etc.). Then copy your backups off the server.

Production best practices

  • Pin a specific image version rather than latest
  • Set restart: unless-stopped and a healthcheck for your services
  • Publish as few ports as possible, and locally behind a reverse proxy when possible
  • Keep your secrets in a protected .env file (chmod 600 .env), out of Git
  • Do not use privileged: true and do not mount /var/run/docker.sock unless necessary
  • Monitor disk space with docker system df
  • Regularly test restoring your backups

Troubleshooting

permission denied on /var/run/docker.sock

Your user is not yet recognized in the docker group. Check with id, then reconnect over SSH.

Conflicting values set for option Signed-By

An old Docker repository configuration remains, often /etc/apt/sources.list.d/docker.list. After checking its contents, delete it:

Terminal
sudo rm /etc/apt/sources.list.d/docker.list
sudo apt update

Cannot connect to the Docker daemon

Terminal
sudo systemctl status docker
sudo journalctl -u docker -n 50 --no-pager
sudo dockerd --validate --config-file=/etc/docker/daemon.json

A syntax error in daemon.json prevents the service from starting.

port is already allocated or address already in use

Another container or service is using this port. Identify it with sudo ss -ltnp | grep ':8080 ' and docker ps, then change the server-side port.

no space left on device

Terminal
df -h
docker system df
docker image prune
docker builder prune

Only use docker volume prune after checking that the volumes concerned no longer contain useful data.

toomanyrequests during a download

The Docker Hub download limit has been reached. Wait, or log in to your account with docker login.

docker-compose: command not found

The current plugin is used with a space: docker compose.

A port remains accessible despite UFW

This is the normal behavior of ports published by Docker. Publish the port on 127.0.0.1 or apply the restrictions from the guide Configure UFW.

References