So unfortunately it failed again...on a docker file again. Before running i found some threads on thinning out docker a bit and freed up some space. It took the supposed backup size to about 12gb instead of 18. I the did a "systemctl stop docker" as well a "stop docker.socket". I then did a "status docker" and it told me it was inactive. I figured this meant i was good to go.
When i went to check on it hours later it showed basically the same error as yesterday. Out of space. That makes me wonder even more because i freed up a good about of space on the sd card and got the backup image size to be smaller.
The only other thing I can think of is that OMV is still somehow running docker because i did install the "Compose" plugin originally and then moved to managing containers with Dockge. Im not sure if this acts as another instance of Docker that was unaffected by the "systemctl" command? If so... i dont know how to stop the OMV version. Though i do know that both OMV Compose and Dockge both always show the same status for any given container.... so i guess they're not completely seperate.
On the plus side the --progress command worked this time. I think i read in another thread that --info=progress2 is a flag for a less verbose version? i was just hoping for a % bar or something so i can tell its still working away. Not necessarily a breakdown of every file its compressing.
When i went to check on it hours later it showed basically the same error as yesterday. Out of space. That makes me wonder even more because i freed up a good about of space on the sd card and got the backup image size to be smaller.
The only other thing I can think of is that OMV is still somehow running docker because i did install the "Compose" plugin originally and then moved to managing containers with Dockge. Im not sure if this acts as another instance of Docker that was unaffected by the "systemctl" command? If so... i dont know how to stop the OMV version. Though i do know that both OMV Compose and Dockge both always show the same status for any given container.... so i guess they're not completely seperate.
On the plus side the --progress command worked this time. I think i read in another thread that --info=progress2 is a flag for a less verbose version? i was just hoping for a % bar or something so i can tell its still working away. Not necessarily a breakdown of every file its compressing.
Statistics: Posted by eikonic — Wed Oct 16, 2024 9:05 pm