I'm thinking about to start using the Openmediavault Compose-plugin.
After weighing up the pros and cons and the benefits of the proposed workflow change, I decided to keep my current one.
Working in the CLI feels far too comfortable.
Current state
Right now I'm managing all my Docker containers using a dedicated user (docker) via docker-compose.yml files within a SSH session.
On one of my ZFS pools I've created the following file systems/shared folders:
- appdata, which houses, within subdirectories, compose files & container specific data
- docker, former location: /var/lib/docker
- backup, backups of appdata
To allow proper usage of ZFS and to promote the new location of the Docker data directory I'm using the following custom daemon.json file:
{
"storage-driver": "zfs",
"data-root": "/mnt/virt/docker"
}
Aimed goals
- Reuse above mentioned directory structure
- Keep my custom daemon.json, realized by an empty Docker storage line within settings dialog of the Compose-plugin if I understood it right
- Reuse my current docker-compose.yml files
- move settings of various container base env-files to a single one and update docker-compose.yml accordingly
Actual question
Will this be as simple as installing the plugin, configure it (the shared folder paths) and regenerate my docker-compose.yml files within the OMV GUI?