You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any clear reason why bind mounts are preferred in the documentation? Would the same benefits (i.e. robustness) be achieved by using volume mounts?
In what kind of a situation would it be necessary to manually manipulate the files persisted by the system modules from the host side?
The text was updated successfully, but these errors were encountered:
The documentation instructs using bind mounts for persistently storing the data of edgeAgent or edgeHub modules on the host filesystem.
Docker's own documentation recommends using volume mounts instead.
Is there any clear reason why bind mounts are preferred in the documentation? Would the same benefits (i.e. robustness) be achieved by using volume mounts?
In what kind of a situation would it be necessary to manually manipulate the files persisted by the system modules from the host side?
The text was updated successfully, but these errors were encountered: