borgmatic check state persistence

[witten]

As of borgmatic 1.7.0, borgmatic stores check state in ~/.borgmatic/checks, which allows the user to configure checks to run on a rough schedule instead of every time borgmatic runs. There is also a default schedule that relies on ~/.borgmatic/checks even if the user doesn't configure anything.

So do you think it makes sense for the Docker image documentation to instruct the user to mount this path as a volume? That way the check state would be persisted across restarts of the container. I realize I was probably the one who told you that ~/.borgmatic doesn't need persisting anymore, so I take responsibility for this even being an issue with the Docker image to begin with!

Tangentially related issue: https://projects.torsion.org/borgmatic-collective/borgmatic/issues/562