21 minutes ago, ZappyZap said:

Possible,
and to be clear, not my container, it is my template but not container.
I will update my unraid and get back to you.

ok, make sense.. Thank you..

any luck?

I am travelling so will be when I get back, I will avoid upgrading unraid while I am away

please open an issue on the container github

ok, no worries =) will wait for update once you are back.

I just realised my PBS was down, I've been running this container for months and now it has the same issue. I tracked down when it failed and I believe it's the same night that I messed up and had to delete my docker.img. The re-deployed PBS container has this issue. I'm fairly confident I was running an up-do-date copy of the docker image before it happened.

The config hasn't changed, the permissions are all user and group 34. I shelled into the container and confirmed that the mappings are working; I also confirmed that the backup user is able to write files to /var/lib/proxmox-backup/rrd and /etc/proxmox-backup.

I think despite the error saying operation not permitted it's not a file permissions error. Something about the move is the operation not permitted, perhaps related to the syslog error?

After poking around a bit more I realised this docker setup was a bit more fragile than I'm comfortable with for critical backups. I've installed PBS into a debian LXC on unraid, using the proxmox apt repo, and migrated the config from appdata into there. Everything seems to be working.

So don't rush to fix this on my account - @Dro might still be waiting though.

Waiting on the dev to release the new version