Skip to Content
Last modified by Erik Bakker on 2024/08/26 12:37
From version 45.1
edited by Erik Bakker
on 2022/10/31 10:43
Change comment: There is no comment for this version
To version 47.1
edited by Erik Bakker
on 2022/10/31 15:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -64,10 +64,28 @@
64 64  
65 65  An alternative option to read and write **persistent** data is to use the "Bind mount" option avaiable. In general we advice to use the "Volume" option because they have better performance and bind mounts are dependent on the directory structure and OS of the host machine. Having said that not all external systems can adapt to this that easily. That is why the "Bind mount" option can be of interest in your use case.
66 66  
67 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-bind-mount.png]]
68 +
67 67  To configure a "Bind mount" you need to define a source and a target directory that are linked to each other. The source directory defines the directory on your local system (that might already be in use currently to exchange files). The target directory defines a directory on your docker installation that can be accessed by the runtime.
68 68  
71 +{{warning}}Note, that when the source directory does not exists the runtimes cannot be deployed correctly.{{/warning}}
72 +
73 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-bind-mount-filled-in.png]]
74 +
75 +{{info}}Note, that when you use this option your directory reference in your flow should refer to the "target" directory configured here.{{/info}}
76 +
69 69  === 3.3 Temporary file system ===
70 70  
79 +If you do not want to work with **persistent** data but have a need for **non-persistent** data the temporary file system option is for you. This way you can increase the container’s performance by avoiding writing into the container’s writable layer.
80 +
81 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-temp-file-storage.png]]
82 +
83 +To configure this option you need a target location. On top of that you can define the maximum size of the temporary file system.
84 +
85 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-temp-file-storage-filled-in.png]]
86 +
87 +{{warning}}We strongly advice to define this number as that way you can limit the potential impact this solution can have on the stability of your machine.{{/warning}}
88 +
71 71  === 3.4 Named pipe ===
72 72  
73 73  The named pipe option can be selected but we yet have to see a valid use case within the context of eMagiz for using this option. Therefore we won't discuss this option further in this microlearning.