How To Update A Container With Docker Compose

How To Update A Container With Docker Compose

Docker Compose is a tool that lets you define and run multiple containers as a single service. It’s great for developing and testing applications that have multiple components, such as a web server, a database, and a cache. I’ll show you how to update a container with Docker Compose in a few simple steps. You’ll learn how to modify the Dockerfile, rebuild the image, and restart the container with the new configuration.

I am having a Plausible installation done with docker-compose that has been almost 1 year since I updated, it was built following the tutorial: Install Plausible Google Analytics and it has the bellow docker compose file:

version: "3.3"
    image: bytemark/smtp
    restart: always

    image: postgres:12
    restart: always
      - db-data:/var/lib/postgresql/data
      - POSTGRES_PASSWORD=postgres

    image: yandex/clickhouse-server:
    restart: always
      - event-data:/var/lib/clickhouse
      - ./clickhouse/clickhouse-config.xml:/etc/clickhouse-server/config.d/logging.xml:ro
      - ./clickhouse/clickhouse-user-config.xml:/etc/clickhouse-server/users.d/logging.xml:ro
        soft: 262144
        hard: 262144

    image: plausible/analytics:latest
    restart: always
    command: sh -c "sleep 10 && / db createdb && / db migrate && / db init-admin && / run"
      - plausible_db
      - plausible_events_db
      - mail
      - 8000:8000
      - plausible-conf.env

    driver: local
    driver: local
    driver: local

Docker Compose Plausible Explination

This is a Docker Compose file written in YAML format, which describes a multi-container application consisting of plausible services: mail, plausible_db, plausible_events_db, and plausible.

The mail service uses the bytemark/smtp image to provide a Simple Mail Transfer Protocol (SMTP) server for sending emails.

The plausible_db service uses the postgres:12 image to provide a PostgreSQL database server. It stores its data in a named Docker volume db-data, and sets the POSTGRES_PASSWORD environment variable to “postgres” for authentication.

The plausible_events_db service uses the yandex/clickhouse-server: image to provide a ClickHouse database server for storing event data. It stores its data in a named Docker volume event-data, and mounts two configuration files from the local file system. It also sets the nofile ulimit to allow for a higher number of open files.

The plausible service uses the plausible/analytics:latest image to provide a web analytics platform. It depends on the plausible_db, plausible_events_db, and mail services, and exposes port 8000 to the host. It also uses an environment file plausible-conf.env to set certain configuration variables. Finally, it runs a command to initialize the database, run migrations, create an admin user, and start the application.

The file defines three named Docker volumes, db-data, event-data, and geoip, which can be used to persist data across container restarts.

All services have the restart option set to always, which ensures that they are automatically restarted if they fail or if the Docker daemon is restarted.

What Will be Updated

If I leave the Docker Compose file untouched, the only container that will receive an update is the plausible service, which runs the latest version of the plausible/analytics image. This is precisely what I’ve been eagerly awaiting - a chance to unlock the full potential of the latest features and enhancements.

Of course, if you’d like to update the other containers as well, you’re more than welcome to do so! Just make sure that you pull the latest image with the latest tag or specify the exact version for the postgres:12 and yandex/clickhouse-server: images. Luckily, in my case, these images are already set to a specific version, so the Docker command will pull the exact image I need to ensure that everything runs smoothly.

What will Happen with the Data

The data for plausible analytics is helled in volumes, so if you check the yml file you see:

      - db-data:/var/lib/postgresql/data
      - event-data:/var/lib/clickhouse
      - ./clickhouse/clickhouse-config.xml:/etc/clickhouse-server/config.d/logging.xml:ro
      - ./clickhouse/clickhouse-user-config.xml:/etc/clickhouse-server/users.d/logging.xml:ro

The actual data is not in the docker image but on the actual VM, so it will just be picked up.

Running The Update Commands

Pull The Latest Docker Images

In function of what you modified you need to run:

 docker compose pull

This command will pul the images that is in docker compose besed on the tags in my case will only update the plausible/analytics:latest

Bellow is the actual output:

Docker Pull Output

Recreate Docker Images

Now that you have the latest docker images downloaded is just a matter of recreating them to use the latest things. To do so you just run:

docker compose up -d

When you run docker-compose up -d, Docker Compose will create and start the containers for all the services defined in the docker-compose.yml file. It will also create any needed networks and volumes if they are defined in the file.

The -d flag tells Docker Compose to run the containers in a detached mode, which means that the containers will run in the background and will not be attached to the terminal. This allows you to continue using the terminal for other tasks while the containers are running.

The output will be:

Docker Up Output

Verify that Containers are Up

Once the containers are started, you can use the docker-compose ps command to check the status of the containers and verify that they are running as expected. You can also use other Docker commands, such as docker logs and docker exec, to interact with the containers and troubleshoot any issues that may arise.

docker-compose ps


docker-compose ps
             Name                            Command               State                    Ports
plausible-mail-1         exim  ...   Up      25/tcp
plausible-plausible-1             / sh -c sleep ...   Up>8000/tcp,:::8000->8000/tcp
plausible-plausible_db-1 postgres    Up      5432/tcp
plausible-plausible_events_db-1   /                   Up      8123/tcp, 9000/tcp, 9009/tcp


That’s all you need to do to have your docker-compose containers updated to the version you need, to be as safe as possible you can do a server backup in case something happens to be able to do a rollback.