Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RESTIC_REPOSITORY_FILE cannot be used #112

Open
nonsavant opened this issue Dec 29, 2021 · 2 comments
Open

RESTIC_REPOSITORY_FILE cannot be used #112

nonsavant opened this issue Dec 29, 2021 · 2 comments
Labels

Comments

@nonsavant
Copy link

Setting a value for RESTIC_REPOSITORY_FILE is ignored and overwritten by the default value of RESTIC_REPOSITORY, rendering the RESTIC_REPOSITORY_FILE environment variable unusable.

Sample docker-compose file snippet:

  restic:
    image: mazzolino/restic
    container_name: restic
    secrets:
      - restic_repository
      - restic_password
    environment:
      BACKUP_CRON: "0 30 3 * * *"
      RESTIC_REPOSITORY_FILE: /run/secrets/restic_repository
      RESTIC_PASSWORD_FILE: /run/secrets/restic_password
      RESTIC_BACKUP_ARGS: "--verbose=2"
      RUN_ON_STARTUP: "true"
    volumes:
       - /data/media:/data

Result of docker inspect:

$ docker inspect restic | grep RESTIC_REPO
                "RESTIC_REPOSITORY_FILE=/run/secrets/restic_repository",
                "RESTIC_REPOSITORY=/mnt/restic"

I guess the fix is something like: If RESTIC_REPOSITORY_FILE is provided, don't set RESTIC_REPOSITORY with the default value.

@djmaze djmaze added the bug label Jan 17, 2022
@stale
Copy link

stale bot commented Mar 30, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Mar 30, 2022
@stale stale bot closed this as completed Apr 16, 2022
@djmaze djmaze removed the wontfix label Apr 18, 2022
@djmaze djmaze reopened this Apr 18, 2022
@stale
Copy link

stale bot commented Jul 10, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jul 10, 2022
@djmaze djmaze removed the wontfix label Aug 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants