Dan Helfman

Note that this unfortunate interaction may go away with borgmatic 1.9.0 because (from the [release notes](https://projects.torsion.org/borgmatic-collective/borgmatic/releases/tag/1.9.0)): * BREAKING: When databases are configured, don't auto-enable the "one_file_system" option, as existing auto-excludes...

In case it's relevant to the discussion of this: https://torsion.org/borgmatic/docs/how-to/upgrade/#versioning-and-breaking-changes

Thanks for filing this! Unfortunately the borgmatic Apprise hook doesn't currently support sending borgmatic logs to Apprise, nor does it support command execution to populate `body`! If you're getting that...

FYI as of borgmatic 1.8.9 (not yet released), the Apprise hook supports sending borgmatic logs to your Apprise services and in fact will do so by default. More details here:...

borgmatic 1.8.9 is now released with this support for Apprise log sending.

I'm not sure what's going on, but I recommend filing a separate issue including your configuration (especially the Apprise section). And describe or paste what you're expecting to see vs....

Sorry for the lengthy delay here. If it's still happening, can you provide the error message you're seeing, along with the command you're running to get it? Seeing your `.env`...

Thanks, that looks like an easy fix. The path is _currently_ deprecated, but it's possible it will [become un-deprecated](https://github.com/borgmatic-collective/docker-borgmatic/issues/211) at some point...

FWIW, I had similar symptoms—Traefik 2.11.18's memory usage growing without bound—and setting `keepAliveMaxTime` didn't seem to help. This was on a much smaller setup, not in K8s.

More anecdata: Early signs are that upgrading to Traefik v3 solved the ever-growing memory usage in my particular case.