A bug was fixed and that's why it is happening now - something that should have happened anyway. There was a thread a few days ago that mentioned the bug and then it was fixed. If you would show your compose file (without any secrets) then people could say if the fix to the bug was the cause for what you're seeing.
I don't think that read only flag has anything to do with the logic of the compose backup.
Solved this by using the # SKIP_BACKUP flag but not sure why this is needed when directories are marked RO and this has only recently started to happen?
I had a typo when making a change to fix another issue. It is fixed in the testing version - test new version of compose plugin that has a docker exec terminal
I really didn't know people were using :ro on so many things other than a single file. Do you have max backup size disabled (set to 0)?
Yes I have max backup size set to 0.
Not disabling this would've likely prevented filling the filesystem.
Don’t have an account yet? Register yourself now and be a part of our community!
