Skip to Content
Last modified by Erik Bakker on 2024/08/26 12:37
From version 43.1
edited by Erik Bakker
on 2022/10/31 10:25
Change comment: There is no comment for this version
To version 46.1
edited by Erik Bakker
on 2022/10/31 11:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -42,7 +42,7 @@
42 42  
43 43  === 3.1 Volume ===
44 44  
45 -The first type available to you is Volume. With this option you create one or more folders on docker that is relevant for that runtime to read and/or write persistent data. To configure this type you need to link the runtime volume to a machine volume that you can create within the same pop-up. This means that you can re-use a "Machine volume" over multiple runtimes (i.e. containers).
45 +The first type available to you is Volume. With this option you create one or more folders on docker that is relevant for that runtime to read and/or write **persistent** data. To configure this type you need to link the runtime volume to a machine volume that you can create within the same pop-up. This means that you can re-use a "Machine volume" over multiple runtimes (i.e. containers).
46 46  
47 47  So, at first we open the tab called "Machine volume". By pressing the "New" button we can define a new "Machine volume". In the pop-up that follows we can define the name of a machine volume and tell whether the volume already exists on your docker installation or not.
48 48  
... ... @@ -62,10 +62,24 @@
62 62  
63 63  === 3.2 Bind mount ===
64 64  
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 +
67 +[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-bind-mount.png]]
68 +
69 +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.
70 +
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 +
65 65  === 3.3 Temporary file system ===
66 66  
67 67  === 3.4 Named pipe ===
68 68  
81 +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.
82 +
69 69  == 4. Assignment ==
70 70  
71 71  Configure an entry in which you build the archiving and the clean up of the archiving.