One volume that's bound to a folder in the compose.yml directory isn't being backed up by the backup script. #67
Description
Sorry for the confusion. Here is the separate issue you asked for:
I don't know what exactly is the problem here, but a volume that's mapped like this doesn't get backed up either:
examplename.yml
services:
examplename:
container_name: examplename
volumes:
- ./examplename:/app/data/
In the backup logs, this volume is never mentioned. Maybe the problem is, that the name of the mapped folder is the same as the name of the compose file? Because in the same file, there is this, that is being backed up:
postgres:
container_name: postgres
volumes:
- ./examplename-pgdata:/var/lib/postgresql/data
Just a proposal:
Wouldn't it make sense to just save the whole folder that contains the yml file including all files and subfolders, and just make sure somehow that any volume, that's mounted from there, doesn't get copied a second time?
Right now the vol.list in the respective backup folder usually says, that folder 0 is the folder of the compose file. But a lot of times it actually doesn't contain the entire folder, but the script only saves the compose.override.yml, the yml and the env file there, even though there might be other files in that folder. (I know, that this is not the intended use of the plugin and the backup script. But sometimes there might be other files there belonging to that compose application.)