ovm-compose installing docker error

  • Ok I've installed OMV 7.4.7-1 (Sandworm) on a Raspberry Pi 4 Model B Rev 1.4...


    I'm trying to install to install docker and this is the error I am getting... Please help



    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color compose 2>&1' with exit code '1': Matriark:


  • crashtest

    Approved the thread.
  • Ok I've installed OMV 7.4.7-1 (Sandworm) on a Raspberry Pi 4 Model B Rev 1.4...

    How did you installed? Which guide did you follow?


    Did you use armhf version or arm64 version of RaspiOS?

  • How did you installed? Which guide did you follow?


    Did you use armhf version or arm64 version of RaspiOS?

    To install Raspberry pi imager to install Raspberry pi OS 64bit

    then used below to install omv7

    Code
    $ wget -O - https://raw.githubusercontent.com/OpenMediaVault-Plugin-Developers/installScript/master/install | sudo bash
  • for rpi there is a preinstall script that needs to be run before the main install script. This will fix an issue with the network config.


    You can fix this manually if it is the issue (not sure from the error message)

  • ok so i reinstalled everything 3 times. Each time doing the same thing and on the 3rd try it worked. to me its just the luck of the draw. the only thing different was i installed compose first before connecting my hard drives.


    thankyou for you help

  • voyix

    Added the Label resolved
    • New
    • Official Post

    the only thing different was i installed compose first before connecting my hard drives.

    ryecoaaron You might be interested in reading this.

    • New
    • Official Post

    You might be interested in reading this.

    Why? Other than a bad order to do things, it shouldn't really make a difference. You can't configure the plugin because you have no shared folders. You need to add the drive(s) to add shared folders. When you finally can configure the compose plugin, it will do the right thing.

    omv 7.4.7-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.3 | k8s 7.2.0-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.8


    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!

    • New
    • Official Post

    Why? Other than a bad order to do things, it shouldn't really make a difference. You can't configure the plugin because you have no shared folders. You need to add the drive(s) to add shared folders. When you finally can configure the compose plugin, it will do the right thing.

    Well, reading what the OP says it seems that he made three installation attempts, two of them failed and the third was successful. And it says that on the third attempt it installed the plugin with the hard drives disconnected. I don't really see much point in it but I thought maybe there was something else to analyze. Looking at your answer it seems that this is not the case.

    • New
    • Official Post

    Well, reading what the OP says it seems that he made three installation attempts, two of them failed and the third was successful. And it says that on the third attempt it installed the plugin with the hard drives disconnected. I don't really see much point in it but I thought maybe there was something else to analyze. Looking at your answer it seems that this is not the case.

    The error in the first post was debian repos (not docker or omv or omv-extras). I don't know what was done wrong but evidently something different was done the third time to not break the debian repos. I have installed OMV on RPis hundreds of times and never had the Debian repos broken. If the RPi install guide is followed exactly, the repos shouldn't be broken. Not sure how to fix this if the guide isn't followed but it isn't the job of the compose plugin to "fix" the debian repos.

    omv 7.4.7-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.3 | k8s 7.2.0-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.8


    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!

    • New
    • Official Post

    Well, reading what the OP says it seems that he made three installation attempts, two of them failed and the third was successful.

    When I look at scenarios like this, what I keep in mind is:

    1. Generally speaking, almost any post on this forum is an "exception scenario". There are literally thousands who are doing the same thing without an issue.
    2. Even with documentation to guide them, many users don't read it, some may chose to see what they want to see (versus reading what is actually there) or they simply do what they want to do.
    3. There are tons of physical variables like power, physical connections, peripheral issues, software sources (off-line or with marginally connected through the internet), etc.

    All of the above can't be accounted for with software. It simply can't be done. Again, generally speaking, when there's a real problem the forum lights up (so to speak) with posts that point to a real issue. I can honestly say, it's truly rare when a single new user finds an actual bug.

    In this case, I'm of the belief that in the last of the 3 attempts, one or more factors previously mentioned cleared up, a mistake wasn't made, etc.

Participate now!

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