Skip to Content
Last modified by Erik Bakker on 2024/08/26 12:37
From version 60.1
edited by Carlijn Kokkeler
on 2023/11/20 15:08
Change comment: There is no comment for this version
To version 59.1
edited by Erik Bakker
on 2023/11/16 07:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -89,10 +89,6 @@
89 89  * In the case of using the Volume option in combination with a Machine volume, the external system with which you exchange data on-premise via a file-based method needs to be able to write or read the data from the volume (i.e., directory) you have configured. Should this be a problem, the Bind mount alternative discussed below should be considered.
90 90  * The Volume option and Machine volume combination can also be used for eMagiz-only information that needs to be persistable, such as archiving.
91 91  * In the case of using the Volume option in combination with a Network volume, the path to read and write from becomes what you define in the target field.
92 -* In case of mapping a volume on a windows host machine to another one on a windows docker runtime when writing the source/target paths, the following small adjustment is required:
93 -** In the source/target path:
94 -a. All “\” in the path should be written as “/”. Example: C:\Users\xxxx\tmp should be written as C:/Users/xxxx/tmp
95 -
96 96  {{/warning}}
97 97  
98 98  === 3.2 Bind mount ===