fix: resolve volume name conflicts in restic stack

Prefixed all external volume references with 'backup_' to avoid
conflicts with volume definitions in other compose files (e.g.,
directus_uploads defined in both sexy and restic).

This allows Docker Compose's include pattern to work correctly
without volume name collisions.
This commit is contained in:
2025-11-06 10:16:52 +01:00
parent c89769a23f
commit acf6385aca

View File

@@ -15,19 +15,19 @@ services:
- ${RESTIC_BACKUP_PATH:-/mnt/hidrive/users/valknar/Backup}:/repos - ${RESTIC_BACKUP_PATH:-/mnt/hidrive/users/valknar/Backup}:/repos
# Docker volumes to backup (read-only) # Docker volumes to backup (read-only)
- core_postgres_data:/volumes/core_postgres_data:ro - backup_core_postgres_data:/volumes/core_postgres_data:ro
- core_redis_data:/volumes/core_redis_data:ro - backup_core_redis_data:/volumes/core_redis_data:ro
- directus_uploads:/volumes/directus_uploads:ro - backup_directus_uploads:/volumes/directus_uploads:ro
- directus_bundle:/volumes/directus_bundle:ro - backup_directus_bundle:/volumes/directus_bundle:ro
- awesome_data:/volumes/awesome_data:ro - backup_awesome_data:/volumes/awesome_data:ro
- gotify_data:/volumes/gotify_data:ro - backup_gotify_data:/volumes/gotify_data:ro
- scrapyd_data:/volumes/scrapyd_data:ro - backup_scrapyd_data:/volumes/scrapyd_data:ro
- scrapy_code:/volumes/scrapy_code:ro - backup_scrapy_code:/volumes/scrapy_code:ro
- n8n_data:/volumes/n8n_data:ro - backup_n8n_data:/volumes/n8n_data:ro
- filestash_data:/volumes/filestash_data:ro - backup_filestash_data:/volumes/filestash_data:ro
- linkwarden_data:/volumes/linkwarden_data:ro - backup_linkwarden_data:/volumes/linkwarden_data:ro
- linkwarden_meili_data:/volumes/linkwarden_meili_data:ro - backup_linkwarden_meili_data:/volumes/linkwarden_meili_data:ro
- letsencrypt_data:/volumes/letsencrypt_data:ro - backup_letsencrypt_data:/volumes/letsencrypt_data:ro
environment: environment:
TZ: ${TIMEZONE:-Europe/Berlin} TZ: ${TIMEZONE:-Europe/Berlin}
@@ -65,43 +65,43 @@ volumes:
name: ${RESTIC_COMPOSE_PROJECT_NAME}_tmp name: ${RESTIC_COMPOSE_PROJECT_NAME}_tmp
# External volumes from other stacks (read-only mounts) # External volumes from other stacks (read-only mounts)
core_postgres_data: backup_core_postgres_data:
name: core_postgres_data name: core_postgres_data
external: true external: true
core_redis_data: backup_core_redis_data:
name: core_redis_data name: core_redis_data
external: true external: true
directus_uploads: backup_directus_uploads:
name: core_directus_uploads name: core_directus_uploads
external: true external: true
directus_bundle: backup_directus_bundle:
name: core_directus_bundle name: core_directus_bundle
external: true external: true
awesome_data: backup_awesome_data:
name: awesome_data name: awesome_data
external: true external: true
gotify_data: backup_gotify_data:
name: messaging_data name: messaging_gotify_data
external: true external: true
scrapyd_data: backup_scrapyd_data:
name: scrapy_scrapyd_data name: scrapy_scrapyd_data
external: true external: true
scrapy_code: backup_scrapy_code:
name: scrapy_scrapy_code name: scrapy_scrapy_code
external: true external: true
n8n_data: backup_n8n_data:
name: n8n_n8n_data name: n8n_n8n_data
external: true external: true
filestash_data: backup_filestash_data:
name: stash_filestash_data name: stash_filestash_data
external: true external: true
linkwarden_data: backup_linkwarden_data:
name: links_data name: links_data
external: true external: true
linkwarden_meili_data: backup_linkwarden_meili_data:
name: links_meili_data name: links_meili_data
external: true external: true
letsencrypt_data: backup_letsencrypt_data:
name: proxy_letsencrypt_data name: proxy_letsencrypt_data
external: true external: true