I would like to backup my vaultwarden with ttionya/vaultwarden-backup. I found the linked docker-compose-file but it does not work in my case.
I just learnt - thanks to u/this_is_router and u/inner - that i store my vaultwarden-data in a local folder in the compose-directory, so in my case the dopcker compose looks like this:
services:
vaultwarden:
image: vaultwarden/server:latest
restart: always
# environment:
# SIGNUPS_ALLOWED: 'false'
# ADMIN_TOKEN: 'your authentication token'
ports:
- '127.0.0.1:8200:80'
volumes:
- ./vaultwarden:/data/
backup:
image: ttionya/vaultwarden-backup:latest
restart: always
# environment:
# RCLONE_REMOTE_NAME: 'BitwardenBackup'
# RCLONE_REMOTE_DIR: '/BitwardenBackup/'
# RCLONE_GLOBAL_FLAG: ''
# CRON: '5 * * * *'
# ZIP_ENABLE: 'TRUE'
# ZIP_PASSWORD: 'WHEREISMYPASSWORD?'
# ZIP_TYPE: 'zip'
# BACKUP_FILE_SUFFIX: '%Y%m%d'
# BACKUP_KEEP_DAYS: 0
# PING_URL: ''
# MAIL_SMTP_ENABLE: 'FALSE'
# MAIL_SMTP_VARIABLES: ''
# MAIL_TO: ''
# MAIL_WHEN_SUCCESS: 'TRUE'
# MAIL_WHEN_FAILURE: 'TRUE'
# TIMEZONE: 'UTC'
volumes:
- ./vaultwarden:/bitwarden/data/
- ./vaultwarden-rclone-data:/config/
# - /path/to/env:/.env
volumes:
vaultwarden-data:
# Specify the name of the volume where you save the vaultwarden data,
# use vaultwarden-data for new users
# and bitwardenrs-data for migrated users
name: vaultwarden-data
vaultwarden-rclone-data:
external: true
# Specify the name of the volume where you save the rclone configuration,
# use vaultwarden-rclone-data for new users
# and bitwardenrs-rclone-data for migrated users
name: vaultwarden-rclone-data
EDIT: Now it runs! I just had to edit the folders. Edited the docker-compose.yml above. Thanks…
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-stoppedIn 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.