Type error with newly initialized repo #857
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#857
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I'm trying to do and why
I am using the official borgmatic Docker container to backup one of my hosts. It is configured to use a repo via ssh:// on a remote backup host (see docker-compose.yml and config.yaml in "Steps to reproduce").
With the destination folder on the destination-host being empty, I execute:
docker compose exec -it borgmatic borgmatic init --encryption repokey
, which seems to work OK:After that, I trigger the first backup using
docker compose exec -it borgmatic borgmatic create --verbosity 1 --list --stats
, which also succeeds:prune
andcompact
also works.But as soon as I execute
check
, I get a TypeError:Steps to reproduce
config.yaml
docker-compose.yml
Actual behavior
Expected behavior
Not receiving a Python Exception
Other notes / implementation ideas
No response
borgmatic version
1.8.10
borgmatic installation method
Container - https://github.com/borgmatic-collective/docker-borgmatic
Borg version
1.2.8 in container, 1.2.4 on repo server
Python version
3.12.3 in container, 3.11.2 on repo server
Database version (if applicable)
No response
Operating system and version
Container Host: Debian 11, Container Image: Alpine Linux v3.19, Repo-Server: Debian 12
PS: I tried to run the individual checks using
--only
, one by one.extract
,repository
andarchives
works fine.data
yields:spot
yields:The traceback with
data
is a known issue that has been fixed in main and will be part of the next release. You can omitdata
from your checks in the meantime.However I have not seen that error with the
spot
check and I will leave this ticket open to investigate that! Thank you for filing this.Okay, the traceback you reported with the spot check has been fixed in main and will be part of the next release. It turns out that it should have been an error, as running the spot check without corresponding configuration isn't supported. However I've changed it from an ugly traceback to a more friendly error message when this occurs. Thanks again for reporting it!
Released in borgmatic 1.8.11!