LachlanUnchained

AI GENERATED:

---

The ttionya/vaultwarden-backup tool is intended to work with Docker volumes. However, you are using a bind mount, not a named volume. Bind mounts refer to the use of local folders to store data, as in your case (./vaultwarden:/data/), while volumes create a specific place within Docker’s own filesystem for the data.

Although this tool is designed for volumes, it might still work with bind mounts if the backup container can access the data directory. You would need to modify the volume line in the Docker Compose file for the backup tool to point to the directory where your bind mount is located, i.e., to point it to your local ./vaultwarden directory.

So, you might want to adjust your docker-compose.yml file like this:

services:
  vaultwarden-backup:
    image: ttionya/vaultwarden-backup:latest
    container_name: vaultwarden-backup
    environment:
      - PUID=1000
      - PGID=1000
      - BACKUP_INTERVAL=12h
      - PRUNE_BACKUPS=7D
    volumes:
      - ./vaultwarden:/vaultwarden:ro
      - ./backups:/backups
    restart: unless-stopped

In this configuration, ./vaultwarden:/vaultwarden:ro line is the key. It mounts your local ./vaultwarden directory to /vaultwarden inside the backup container (readonly mode), which should allow the backup tool to access the data.