- You have used the
-voption instead of--mount, as described in the documentation.
The difference is very dangerous for your case: if docker will not map the disk to the container for any reason, with the-voption it will create an empty disk inside the container. The customers’ data will be stored inside this container. When you then remove the container, the data will be removed with it.
In case of--mountit will just fail. Please, replace the-voptions to the--mountoptions ASAP. The--mountoption has a different syntax. Please, read about it in the section Running the Storage Node of our Documentation. - You have used an GUI automount option (your disk is mounted inside the
/media), which works only after login. Moreover, it can mount to a different folder every time.
After reboot, the container will be started before the GUI automount has happened and your node will start to store the data inside the mountpoint instead of the disk. Your node will fail too many audits until you log in. After the login, the data in the mountpoint will be hidden. And you will fail audits again but this time, because the hidden data is inaccessible.
Please, use only static mount for the storage. You can read more here
Please, fix both of these problems ASAP and keep your node online.
For more details, please check Please, update your `docker run` command!