Docker compose update erased the database

[brunoamaral]

⚠️ Please verify that this question has NOT been raised before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

📝 Describe your problem

Maybe this was a miss step on my part.

docker-compose.yaml

services:
  uptime-kuma:
    image: louislam/uptime-kuma:1
    container_name: uptime-kuma
    volumes:
      - ./data:/app/data
    ports:
      - "3002:3001"
    restart: always

Then when updating with docker compose pull, docker compose up -d the container was recreated and the database left blank.

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

1.23.16

💻 Operating System and Arch

Ubuntu 22.04.5

🌐 Browser

Any

🖥️ Deployment Environment

• Runtime: Docker version 27.4.0, build bde2b89
• Database: sqlite
• Filesystem used to store the database on: ext4
• number of monitors: 5 - 7.

[homelab-alpha]

@brunoamaral, To ensure data is stored persistently in Docker, you need to map a folder in the docker-compose.yml file. Replace /your/storage/location with a path that fits your system structure.

Example Configuration:

volumes:
  - /your/storage/location/uptime-kuma:/app/data

This setup ensures that data within the container is preserved across restarts and upgrades.

[brunoamaral]

@homelab-alpha that is already a part of my docker-compose.yaml:

    volumes:
      - ./data:/app/data

And still the data didn't persist for some reason.

[homelab-alpha]

@brunoamaral, There is a difference between:

volumes:
  - ./data:/app/data

and:

volumes:
  - /your/storage/location/uptime-kuma:/app/data

With your approach (./data:/app/data), the compose file needs to be located in the same folder structure as the specified directory (./data). This makes it dependent on the location of the compose file.

With my suggestion (/your/storage/location/uptime-kuma:/app/data), this dependency is eliminated, and the chance of making a mistake is significantly smaller. You can explicitly define the storage location independently of the compose file.

EDIT:

By default, Uptime Kuma uses kuma.db as the database name.

Below are the commands to search for the kuma.db file across different operating systems:

Ubuntu / Debian / RHEL / Fedora (Linux)

find / -name kuma.db

Windows (PowerShell)

Get-ChildItem -Recurse -Filter kuma.db -Path C:\

macOS

sudo find / -name kuma.db

On Linux and macOS, the find command is used to search starting from the root (/). On Windows, the Get-ChildItem command in PowerShell is the appropriate option.

As long as the database hasn’t been permanently deleted, you can locate the Uptime Kuma Database.