Add basic dynamic configuration with volume labels #258
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #256
This PR add a basic docker discovery system to autorestic. Autorestic can now connect to a docker daemon, check for volumes with a
autorestic.enableset to1ortrueand backup to the backend configured inautorestic.tolabel. You can also specify a cron inautorestic.cronlabel.This service discovery is only enabled when the
--docker-discoveryflag is set.Since I am used to work with podman and autorestic use the docker command, I needed to add a
--docker-hostflag used to change the host used in the docker command if specified (unix:///var/run/user/1000/podman/podman.sockfor me when working with the podman user socket)The app still need a static configuration file to configure backends and global options. You can also use location both in the static configuration file and docker labels. The new behavior just append the dynamic configuration to the config variable after parsing the config file.
This PR is in draft mode because I would like your suggestions about this feature.