Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| omv6:omv6_plugins:docker_compose [2023/12/28 10:14] – [Settings] chente | omv6:omv6_plugins:docker_compose [2024/04/27 17:22] (current) – chente | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | {{indexmenu_n> | + | {{indexmenu_n> |
| \\ | \\ | ||
| + | |||
| + | < | ||
| + | < | ||
| + | < | ||
| + | |||
| < | < | ||
| Line 74: | Line 79: | ||
| * In the **Shared Folder** field select a shared folder. | * In the **Shared Folder** field select a shared folder. | ||
| * You can choose a shared folder if you have already created it or create it directly by pressing the " | * You can choose a shared folder if you have already created it or create it directly by pressing the " | ||
| - | * Since the openmediavault-sharerootfs plugin is a dependency of the openmediavault-compose plugin, you can create this folder in the root of the OMV system disk if you need to do so. | ||
| * By default these folders and files will be created with permissions restricted to root only. If you need to customize these permissions you can do so through the rest of the available fields. These permissions will not affect subfolders belonging to volumes with relative paths. | * By default these folders and files will be created with permissions restricted to root only. If you need to customize these permissions you can do so through the rest of the available fields. These permissions will not affect subfolders belonging to volumes with relative paths. | ||
| * Click the **Save** button if you have already finished configuring the parameters in this tab. | * Click the **Save** button if you have already finished configuring the parameters in this tab. | ||
| Line 85: | Line 89: | ||
| * The plugin will use this path if we use the CHANGE_TO_COMPOSE_DATA_PATH string in any compose file. This behavior is similar to that of a global environment variable. | * The plugin will use this path if we use the CHANGE_TO_COMPOSE_DATA_PATH string in any compose file. This behavior is similar to that of a global environment variable. | ||
| * To define this folder do the following: | * To define this folder do the following: | ||
| - | * In the Shared Folder field select a shared folder. | + | * In the **Shared Folder** field select a shared folder. |
| * You can choose a shared folder if you have already created it or create it directly by pressing the “+” button on the right. | * You can choose a shared folder if you have already created it or create it directly by pressing the “+” button on the right. | ||
| * Click the **Save** button if you have already finished configuring the parameters in this tab. | * Click the **Save** button if you have already finished configuring the parameters in this tab. | ||
| Line 617: | Line 621: | ||
| ---- | ---- | ||
| - | ===== Schedule ===== | + | ===== Schedule |
| {{ : | {{ : | ||
| Line 764: | Line 768: | ||
| === How to generate a composition yaml file with Autocompose === | === How to generate a composition yaml file with Autocompose === | ||
| \\ | \\ | ||
| - | * Go to **Services** > **Compose** > **Files** and press the **Autocompose** button | + | * Go to **Services** > **Compose** > **Files** and press the **+** and then the **Autocompose** button |
| * Expand the **Container** field. A list of all running containers will appear, select the container you want to generate a //yaml// file for. | * Expand the **Container** field. A list of all running containers will appear, select the container you want to generate a //yaml// file for. | ||
| * In the **Name** field, type the name you want to use for the generated file. | * In the **Name** field, type the name you want to use for the generated file. | ||