Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| omv8:docker_in_omv [2025/12/21 20:01] – [1. Choose a container] chente | omv8:docker_in_omv [2026/01/11 07:30] (current) – [1. Choose a container] chente | ||
|---|---|---|---|
| Line 196: | Line 196: | ||
| < | < | ||
| </ | </ | ||
| - | Installing OMV on a USB flash drive may seem unusual to newcomers, but you may be surprised to learn that many professional-grade servers boot directly from USB devices.< | + | Installing OMV on a USB flash drive (or SD card) may seem unusual to newcomers, but you may be surprised to learn that many professional-grade servers boot directly from USB devices.< |
| This approach provides several advantages and no drawbacks:< | This approach provides several advantages and no drawbacks:< | ||
| <ul> | <ul> | ||
| Line 373: | Line 373: | ||
| *...< | *...< | ||
| </ | </ | ||
| - | In the system diagram of this document, the < | + | In the system diagram of this document, the < |
| - | 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, | + | <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, |
| + | <li>If you prefer, you can place this folder directly on your backup drive instead — both approaches are valid.</ | ||
| + | </ul> | ||
| </ | </ | ||
| Line 398: | Line 400: | ||
| Warning | Warning | ||
| </ | </ | ||
| - | < | + | < |
| - | If you need to place it on < | + | < |
| - | < | + | <li>If you need to place it on < |
| - | Do not place the Docker folder in a < | + | <li>< |
| - | If the only storage available is inside a mergerfs pool, you may: | + | <li>Do not place the Docker folder in a < |
| - | - 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. | + | - 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. | + | - Avoid using mergerfs rebalance on that pool, as it may move Docker’s files to another drive and break Docker.< |
| + | - Alternatively, | ||
| + | </ul> | ||
| </ | </ | ||
| *...< | *...< | ||
| </ | </ | ||
| - | You can < | + | You can < |
| - | This is required, for example, to configure an NVIDIA GPU driver or to set a custom storage driver for certain filesystems.< | + | < |
| - | If you need to customize this file, simply < | + | <li>This is required, for example, to configure an NVIDIA GPU driver or to set a custom storage driver for certain filesystems.< |
| + | <li>If you need to customize this file, simply < | ||
| </ | </ | ||
| Line 523: | Line 528: | ||
| < | < | ||
| </ | </ | ||
| - | 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.< |
| + | If you notice any recent changes, you can report them in the forum for updates. | ||
| </ | </ | ||
| \\ | \\ | ||
| Line 567: | Line 573: | ||
| <ul> | <ul> | ||
| < | < | ||
| - | < | + | < |
| < | < | ||
| < | < | ||
| Line 587: | Line 593: | ||
| environment: | environment: | ||
| - PUID=${{ uid:" | - PUID=${{ uid:" | ||
| - | - PGID=${{ gid:"appuser" }} <FONT COLOR=" | + | - PGID=${{ gid:"users" }} <FONT COLOR=" |
| - TZ=${{ tz }} < | - TZ=${{ tz }} < | ||
| #- JELLYFIN_PublishedServerUrl=192.168.0.5 | #- JELLYFIN_PublishedServerUrl=192.168.0.5 | ||
| Line 615: | Line 621: | ||
| * < | * < | ||
| * PUID and PGID correspond to the UID and GID of the user who will manage the container. | * PUID and PGID correspond to the UID and GID of the user who will manage the container. | ||
| - | * In our case we want this user to be // | + | * In our case, we want this user to be // |
| * < | * < | ||
| PUID=${{ uid:" | PUID=${{ uid:" | ||
| - | PGID=${{ gid:"appuser" }} | + | PGID=${{ gid:"users" }} |
| </ | </ | ||
| * To verify these values: | * To verify these values: | ||
| Line 838: | Line 844: | ||
| environment: | environment: | ||
| - PUID=${{ uid:" | - PUID=${{ uid:" | ||
| - | - PGID=${{ gid:"appuser" }} | + | - PGID=${{ gid:"users" }} |
| - TZ=${{ tz }} | - TZ=${{ tz }} | ||
| - | - SETTINGS_ENCRYPTION_KEY="MyKeyOMV8" | + | - SETTINGS_ENCRYPTION_KEY=MyKeyOMV8 |
| #- CLI_ARGS= #optional | #- CLI_ARGS= #optional | ||
| #- DUPLICATI__WEBSERVICE_PASSWORD= #optional | #- DUPLICATI__WEBSERVICE_PASSWORD= #optional | ||
| Line 876: | Line 882: | ||
| environment: | environment: | ||
| - PUID=${{ uid:" | - PUID=${{ uid:" | ||
| - | - PGID=${{ gid:"appuser" }} | + | - PGID=${{ gid:"users" }} |
| - TZ=${{ tz }} | - TZ=${{ tz }} | ||
| volumes: | volumes: | ||
| Line 1046: | Line 1052: | ||
| environment: | environment: | ||
| - APACHE_PORT=11000 | - APACHE_PORT=11000 | ||
| - | - NEXTCLOUD_DATADIR=${{ sf:data }}/ | + | - NEXTCLOUD_DATADIR=${{ sf:"data" |
| volumes: | volumes: | ||
| nextcloud_aio_mastercontainer: | nextcloud_aio_mastercontainer: | ||
| Line 1168: | Line 1174: | ||
| < | < | ||
| - | < | + | < |
| - | //(where USERNAME is the name of the existing user)// | + | //(where USERNAME is the name of the existing |
| The plugin will automatically replace these expressions with the UID and GID values belonging to the user with that USERNAME. | The plugin will automatically replace these expressions with the UID and GID values belonging to the user with that USERNAME. | ||
| * For example, if the user //peter// has the values '' | * For example, if the user //peter// has the values '' | ||
| < | < | ||
| - | - PGID=${{ gid:"peter" }}</ | + | - PGID=${{ gid:"users" }}</ |
| * will be automatically replaced by: | * will be automatically replaced by: | ||
| < | < | ||