What is the correct process to configure openmediavault-compose?

    • Official Post

    I am doing some tests in OMV7 and I encounter this when configuring compose, I seem to remember that in OMV6 it did not give this error.

    What I do is:

    - Create shared folders for Compose Files, Data and Docker.

    - Copy the absolute path of the Docker shared folder to the Docker field

    - Select the shared folders created for Compose Files and Data

    - Press the Save button

    - Accept changes in Salt

    It gives me the following error:

    Code
              ID: docker
        Function: service.running
          Result: False
         Comment: Failed to start docker.service: Unit docker.service not found.
         Started: 14:58:59.468130
        Duration: 55.126 ms
         Changes:

    Complete error:

    After that error I can press the Reinstall docker button and everything works normally. But in OMV6 I don't remember this being like that.

    Has anything changed in OMV7? I seem to remember that the procedure was like this and it did not give this error.

  • chente

    Added the Label OMV 7.x (Beta)
    • Official Post

    Has anything changed in OMV7? I seem to remember that the procedure was like this and it did not give this error.

    I didn't change anything but I have seen this on the forum for OMV 6.x and previous versions though. I will have to try to recreate and see if there is something I can optimize.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    I'm guessing it happens because the daemon.json file is created after installing the packages. The package installation starts the service in the default location if the daemon.json file doesn't exist. I can reverse the order and it might help.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    Would that cause the default installation to /var/lib/docker and then relocation? That would not be desirable.

    Although it's better than having a error.

    • Official Post

    Would that cause the default installation to /var/lib/docker and then relocation? That would not be desirable.

    Actually that is what it is doing now on systems that don't have docker installed. I am looking at improving it right now.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    let me know if you want me to do tests.

    I tested it on a fresh install but here is the package - https://omv-extras.org/testing…ult-compose_7.0.3_all.deb

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    I tested it on a fresh install but here is the package - https://omv-extras.org/testing…ult-compose_7.0.3_all.deb

    It works perfect. :thumbup: Docker installed without errors in its correct location and the /var/lib/docker folder does not exist in rootfs after configuration.

  • chente

    Added the Label resolved
    • Official Post

    7.0.3 is in the repo.

    omv 8.1.1-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.7 | compose 8.1.5 | cterm 8.0 | borgbackup 8.1.7 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    I guess this also may occur for 6.x :

    Probably yes. But don't worry, if you need to press the Reinstall docker button you can do it and everything will be fine. You will simply have the /var/lib/docker folder in rootfs with some useless files but it does not affect you at all. This will no longer happen in OMV7.

    • Official Post

    In fact, I just saw that I wrote it like this in the documentation a long time ago, I will have to change that text, it is no longer necessary to press that button. https://wiki.omv-extras.org/do…ins:docker_compose#docker


    Edit: It is already modified.

  • Thanks.

    So this mean that the system thinks docker is not enabled but it is in fact ?


    I am not sure I understand what you mean by :

    You will simply have the /var/lib/docker folder.


    If do not change the default docker path (/var/lib/docker) and if I have the error message and if I do not press Reinstall docker, I guess it will be fine. Or am I missing something ?

    • Official Post

    It is advisable to have docker installed on a different drive than rootfs for several reasons. Among them, when reinstalling you will not lose data. Also the docker folder could fill your rootfs. Additionally, if you have OMV installed on a pendrive you will avoid excessive writing. Etc.

    That's why the plugin allows you to change the default location /var/lib/docker to another location.

    If you prefer to leave docker in its default location simply do not modify that field.

    When you have everything configured, press the Reinstall Docker button and everything will work with the parameters you have configured, don't worry about anything else.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!