Differences

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

--- omv8:docker_in_omv [2026/01/11 07:02] – [2.3 CONFIGURATION] chente
+++ omv8:docker_in_omv [2026/01/11 07:30] (current) – [1. Choose a container] chente
@@ Line 373: / Line 373: @@
     *...<html><body><table width="100%" border="0"><tr><td colspan="2" style="background-color:#69A5FF;height:30px;"><strong><span style="color:#FFFFFF;font-size:110%;">&#160; Note
 </span></strong></td></tr><tr><td style="background-color:#E6FEFF;padding:10px;width:380px;">
-In the system diagram of this document, the <i>backup_compose</i> folder is located on the NVMe drive rather than on the dedicated backup drive.<br><br>
+In the system diagram of this document, the <i>backup_compose</i> folder is located on the NVMe drive rather than on the dedicated backup drive.<br>
-The plugin’s scheduled backup function is designed to produce a consistent and up-to-date copy of your persistent data by temporarily stopping the containers during the backup and starting them again afterward. Since each backup overwrites the previous one, this folder is ideal for use together with a separate backup application, which can then create versioned and/or compressed backups <b>without needing to stop the containers</b>.<br><br>
+<ul>
-If you prefer, you can place this folder directly on your backup drive instead — both approaches are valid.
+<li>The plugin’s scheduled backup function is designed to produce a consistent and up-to-date copy of your persistent data by temporarily stopping the containers during the backup and starting them again afterward. Since each backup overwrites the previous one, this folder is ideal for use together with a separate backup application, which can then create versioned and/or compressed backups <b>without needing to stop the containers</b>.</li>
+<li>If you prefer, you can place this folder directly on your backup drive instead — both approaches are valid.</li>
+</ul>
 </tr></table></body></html>
@@ Line 398: / Line 400: @@
 Warning
 </span></strong></td></tr><tr><td style="background-color:#FFE4A6;padding:10px;width:380px;">
-<b>The filesystem hosting the docker folder should preferably be EXT4</b>.<br>
+<b>The filesystem hosting the docker folder should preferably be EXT4</b>.<br><br>
 <ul>
 <li>If you need to place it on <b>ZFS</b> or <b>BTRFS</b> file system, consult the official Docker documentation for the required configuration.</li>
 <li><b>Never use an NTFS</b> file system for Docker data — it does not work and will lead to failures. (or generally for anything on linux other than a staging mount for copying data).</li>
-<li>Do not place the Docker folder in a <b>mergerfs</b> pool, as Docker will spread its internal files across multiple drives, eventually causing corruption or operational problems.<br></li>
+<li>Do not place the Docker folder in a <b>mergerfs</b> pool, as Docker will spread its internal files across multiple drives, eventually causing corruption or operational problems. If the only storage available is inside a mergerfs pool, you may:<br>
-<li>If the only storage available is inside a mergerfs pool, you may:<br>
 - Create the Docker folder directly on a specific drive that belongs to the pool instead of inside the pool, and configure the plugin using the absolute path of that drive.<br>
-- Avoid using mergerfs rebalance on that pool, as it may move Docker’s files to another drive and break Docker.</li>
+- Avoid using mergerfs rebalance on that pool, as it may move Docker’s files to another drive and break Docker.<br>
+- Alternatively, configure the pool by merging folders instead of file systems and place the Docker folder outside of those paths. See the mergerfs documentation on this wiki.</li>
 </ul>
 </tr></table></body></html>
     *...<html><body><table width="100%" border="0"><tr><td colspan="2" style="background-color:#2C6700;height:30px;"><strong><span style="color:#FFFFFF;font-size:110%;">&#160; Advanced configuration.
 </span></strong></td></tr><tr><td style="background-color:#e7fae1;padding:10px;width:380px;">
-You can <b>manually edit /etc/docker/daemon.json to customize</b> Docker’s behaviour.<br>
+You can <b>manually edit /etc/docker/daemon.json to customize</b> Docker’s behaviour.<br><br>
-This is required, for example, to configure an NVIDIA GPU driver or to set a custom storage driver for certain filesystems.<br>
+<ul>
-If you need to customize this file, simply <b>leave the Docker storage field empty</b> in the plugin settings — the plugin will not modify the file.<br>
+<li>This is required, for example, to configure an NVIDIA GPU driver or to set a custom storage driver for certain filesystems.</li>
+<li>If you need to customize this file, simply <b>leave the Docker storage field empty</b> in the plugin settings — the plugin will not modify the file.</li>
 </tr></table></body></html>
@@ Line 525: / Line 528: @@
 <html><body><table width="100%" border="0"><tr><td colspan="2" style="background-color:#69A5FF;height:30px;"><strong><span style="color:#FFFFFF;font-size:110%;">&#160; Note
 </span></strong></td></tr><tr><td style="background-color:#E6FEFF;padding:10px;width:380px;">
-Verify on the official page that this compose file has not changed before installing it
+Verify on the official page that this compose file has not changed before installing it.<br>
+If you notice any recent changes, you can report them in the forum for updates.
 </tr></table></body></html>
 \\