Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| omv6:docker_in_omv [2023/10/16 09:34] – [4. Create the user "appuser"] chente | omv6:docker_in_omv [2024/04/27 17:17] (current) – chente | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | < | + | {{indexmenu_n> |
| + | < | ||
| \\ | \\ | ||
| - | + | < | |
| - | [[omv6: | + | < |
| + | < | ||
| + | [[omv6: | ||
| ---- | ---- | ||
| \\ | \\ | ||
| \\ | \\ | ||
| - | ====== Docker in OMV ====== | + | ====== Docker in OMV 6 ====== |
| \\ | \\ | ||
| \\ | \\ | ||
| 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 350: | Line 353: | ||
| === 4. Create the user " | === 4. Create the user " | ||
| \\ | \\ | ||
| + | {{ : | ||
| * 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 **// | * Define **// | ||
| Line 377: | 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 | + | * You can see the values of user // |
| * In this case we don't need it since we have defined the DATA folder in the plugin GUI at **Services**> | * In this case we don't need it since we have defined the DATA folder in the plugin GUI at **Services**> | ||