Hello,
I am encountering the same issue described here, which was resolved by downgrading to Barman 3.11.1, as mentioned in this pull request.
Would it be possible to use Barman 3.11.1 in the timescaledb-docker-ha images as well as a temporary workaround ?
Thanks,