omv6:docker_in_omv

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
omv6:docker_in_omv [2023/10/16 09:19] – [Summary] chenteomv6:docker_in_omv [2024/04/27 17:17] (current) chente
Line 1: Line 1:
-<html><center><span style="color:#000066;font-size:300%;">Docker in OMV</span></center></html>+{{indexmenu_n>8}} 
 +<html><center><span style="color:#000066;font-size:300%;">Docker in OMV 6</span></center></html>
 \\ \\
- +<html><center><span style="font-size:150%;"> 
-[[omv6:docker_in_omv|{{ :omv6:dockeromv10.jpg?direct&400 |Docker in OMV}}]]+<b>Link to</b> → <a href="https://wiki.omv-extras.org/doku.php?id=omv7:docker_in_omv">Docker in OMV 7</a><br> 
 +<br/></span></center></html> 
 +[[omv6:docker_in_omv|{{ :omv6:dockeromv10.jpg?direct&400 |Docker in OMV 6}}]]
  
 ---- ----
 \\ \\
 \\ \\
-====== Docker in OMV ======+====== Docker in OMV ======
 \\ \\
 \\ \\
Line 108: Line 111:
     * If the drive is fast, like an **SSD or nmve**, applications will run faster.     * If the drive is fast, like an **SSD or nmve**, applications will run faster.
     * Make sure you have **enough space**, the docker folder can take up a lot of space. 60GB may be an acceptable minimum depending on what you are going to install.     * Make sure you have **enough space**, the docker folder can take up a lot of space. 60GB may be an acceptable minimum depending on what you are going to install.
-    * **mergerfs** is not suitable for hosting the docker folder spanned across multiple disks. If you don't have alternatives you can use one of the disks in the pool instead of the pool to host the folder. If you want to do it this way create a folder in the mount path of one of the disks instead of using the pool path. This way the mergerfs logic will disappear from the docker procedures.+    * **mergerfs** is not suitable for hosting the docker folder spanned across multiple disks. If you don't have alternatives you can use one of the disks in the pool instead of the pool to host the folder. If you want to do it this way create a folder in the mount path of one of the disks instead of using the pool path. This way the mergerfs logic will disappear from the docker procedures. If you do this never use the mergerfs leveling tool, doing so will break docker.
     * **BTRFS and ZFS** have incompatibilities with docker. They can be used to host the docker folder but doing so requires additional actions. You can consult the docker documentation if you want to use these file systems, in both cases it can be solved by creating block devices.     * **BTRFS and ZFS** have incompatibilities with docker. They can be used to host the docker folder but doing so requires additional actions. You can consult the docker documentation if you want to use these file systems, in both cases it can be solved by creating block devices.
     * **NTFS** is prohibited. Docker won't work. Do not use NTFS to host docker folders or you will have permissions issues. Always use native Linux file systems.     * **NTFS** is prohibited. Docker won't work. Do not use NTFS to host docker folders or you will have permissions issues. Always use native Linux file systems.
Line 231: Line 234:
 === Why use global environment variables === === Why use global environment variables ===
  
 +  * If you change a path or any other variable that affects multiple containers, it is enough to vary this value in the global environment variables file. The value will change automatically in all containers. Useful if you change a data drive, or if you reinstall OMV and change routes, for example.
   * It is integrated into the plugin, it is enough to press a button to access the file to directly introduce the variables without doing anything else.   * It is integrated into the plugin, it is enough to press a button to access the file to directly introduce the variables without doing anything else.
   * They allow us to define a value once and all the containers that we create will use this value automatically.   * They allow us to define a value once and all the containers that we create will use this value automatically.
Line 349: Line 353:
 === 4. Create the user "appuser" === === 4. Create the user "appuser" ===
 \\ \\
 +{{ :omv6:dockeromv16.jpg?direct&400|UID-GID}}
   * In the OMV GUI go to **Users** > **Users** click on the **+Create** button   * In the OMV GUI go to **Users** > **Users** click on the **+Create** button
-    * Define **//appuser//** name+    * Define **//appuser//** name (or whatever you want to call it).
     * Assign password.     * Assign password.
     * In the groups field we add it to the //users// group (He is probably already in that group, at the time of writing the OMV GUI does this by default).     * In the groups field we add it to the //users// group (He is probably already in that group, at the time of writing the OMV GUI does this by default).
Line 376: Line 380:
   * Replace the values ​​with the appropriate ones in your case.   * Replace the values ​​with the appropriate ones in your case.
     * You can see your local configuration in **System** > **Date & Time** in **//Time zone//** field.     * You can see your local configuration in **System** > **Date & Time** in **//Time zone//** field.
-    * You can see the values ​​of user appdata in **Users** > **Users** in the UID and GID columns.+    * You can see the values ​​of user //appuser// in **Users** > **Users** in the UID and GID columns.
   * In this case we don't need it since we have defined the DATA folder in the plugin GUI at **Services**>**Compose**>**Settings**. But if you need to define other different routes you can also do it here in the same way as the rest of the variables.   * In this case we don't need it since we have defined the DATA folder in the plugin GUI at **Services**>**Compose**>**Settings**. But if you need to define other different routes you can also do it here in the same way as the rest of the variables.
  
  • omv6/docker_in_omv.1697447994.txt.gz
  • Last modified: 2023/10/16 09:19
  • by chente