Hello everyone,
I am running OMV 4.1.23-1 on Raspberry Pi (both 3 and 4) to try and experiment a bit with docker etc.
The question I have is not 100% about docker but more about the structure of the OMV Plugins.
I am struggling to understand the full architecture of the files for each plugin and what a user is supposed to modify and what will be inevitably overwritten during an update.
Example:
I would like to change the command used to start the Docker Daemon from this:
/usr/bin/dockerd -H unix:///var/run/docker.sock -g /srv/dev-disk-by-id-mmc-00000_0xf5e95df9-part3/docker
to this (adding the -H option to expose the docker daemon API in my network:
/usr/bin/dockerd -H unix:///var/run/docker.sock -H tcp:///0.0.0.0:2375 -g /srv/dev-disk-by-id-mmc-00000_0xf5e95df9-part3/docker
By looking at the plugin repository (https://github.com/OpenMediaVa…openmediavault-docker-gui) I have noticed that the commandline options for the services are set in the "etc/systemd/system/docker.service.d/openmediavault.conf" file.
I have tried to manually modify the file in my instllation as follow, hoping that it would result into the desiderd command:
[Service]
EnvironmentFile=-/etc/default/docker
ExecStart=
ExecStart=/usr/bin/dockerd -H unix:///var/run/docker.sock -H tcp://0.0.0.0:2375 $DOCKER_OPTS \
$OMVDOCKER_IMAGE_PATH
Unfortunately, upon service restart the commandline options are still the old ones.
Can someone tell me what I am doing wrong? I have the feeling I am following a convoluted path to achieve something that might be obtained in a simpler way.
Thanks!