All system can fail, and failed system should be recovered. That's why we have disaster recovery plan, back up or replication etc.
(I have just shallow knowledge in docker volume, so please reply if not corrects exist)
I understand docker with local volume is just abstracted file system have mounted path that volume specified linked with host path.
So file i/o is probably not a problem in local volume.
And if network has bug that make data corruption can make difference between nodes, docker cannot be used any system. So we can think network bug may not make data corruption(but can make network separation).
Now I am building on-premise autometic deploying software using Kubernetes as a outsourcing job, so I tried to find SAN for resolving stateful data. After many searching, I realize only local path will guarantee stability of database filesystem. So we mark storage node, and all type of stateful app(limited kinds by playform) is deploied on that node. So we can easily back up and manage storages.
As a deployment manager and backup automation, container for database have a great functionality. All file produced by container are jailed where I specified and can be copied or backed up.
(for stabaility, replication is first class. pause-backup-resume or copying on running will make operational unstability. you can use both for backup, replication first and make backup using that replication node)
go get github.com/blackss2/utility/convert * don't use for production