Almost All Containers in Docker are "Connection Refused"

    • OMV 4.x
    • Almost All Containers in Docker are "Connection Refused"

      I have NextCloud with remote access (as per TechnoDad's tutorial) running, and it works fine (Nextcloud, Letsencrypt, Mariadb, and Duckdns), as well as a Plex server in Docker. Any other container I try to run (Syncthing, Zoneminder, MotionEye) I get "Connection Refused" or "Refused to connect" when I try to open the GUI for any of them. I noticed that if I refresh the docker page in OMV, that the status of those containers always say "Restarting."

      I don't know where to begin to fix this. I had given up on Syncthing in Docker and installed the plugin instead (which works fine). But I need docker for either Zoneminder or MotionEye.
    • geaves wrote:

      threehappypenguins wrote:

      I noticed that if I refresh the docker page in OMV, that the status of those containers always say "Restarting."
      Usually that could be a misconfiguration or the wrong image being used.
      How would I even attempt to find out if it's a misconfiguration? I'm also following the TechnoDad tutorials exactly. And by wrong image, do you mean when I use the search box in the far right of docker? For example, if I'm trying to install Syncthing, there's syncthing/syncthing or linuxserver/syncthing. If that is the case, I'm not installing the wrong image. Again, I follow the TechnoDad tutorials exactly. For syncthing, I installed syncthing/syncthing. When that didn't work, I tried linuxserver/syncthing anyway, but same issue.
    • threehappypenguins wrote:

      And by wrong image, do you mean when I use the search box in the far right of docker?
      The Tag as this will state/apply to the architecture i.e. latest is usually amd64, I pulled the following from github;
      docker pull ccrisan/motioneye:master-amd64
      docker pull ccrisan/motioneye:master-armhf
      As you can see for this one there is two distinct versions.
      Raid is not a backup! Would you go skydiving without a parachute?
    • geaves wrote:

      threehappypenguins wrote:

      And by wrong image, do you mean when I use the search box in the far right of docker?
      The Tag as this will state/apply to the architecture i.e. latest is usually amd64, I pulled the following from github;docker pull ccrisan/motioneye:master-amd64
      docker pull ccrisan/motioneye:master-armhf
      As you can see for this one there is two distinct versions.
      I have no idea what to do, still. I followed the TechnoDad tutorial, which had me installing jshridha/motioneye, for example.
    • geaves wrote:

      Here's a link to linuxserver/syncthing tags as you cansee there are specific tags for specific hardware and you have to use that tag to get the right one.
      I honestly don't understand. How do I "use the tag to get the right one"? I don't know what that means. I have an Odroid HC2. I see in the tags stuff like "arm64," "arm32," and different versions. But when I go to install an image, I'm just choosing the image and clicking "pull." Do I need to do something beyond that and choose arm64 or arm32 from within that image and only pull that somehow? Why doesn't the tutorial explain any of this? Are all these images just incompatible with my Odroid HC2? I don't understand what to do.
    • threehappypenguins wrote:

      I have an Odroid HC2. I see in the tags stuff like "arm64,"
      I think the HC2 would be arm64-latest so when you select an image such as linuxserver/syncthing there is another box next to it, that is the tag box in there you would enter arm64-latest then click start.

      If you don't enter anything in the tag field it will just pull the latest image which is usually amd64.
      Raid is not a backup! Would you go skydiving without a parachute?
    • geaves wrote:

      threehappypenguins wrote:

      I have an Odroid HC2. I see in the tags stuff like "arm64,"
      I think the HC2 would be arm64-latest so when you select an image such as linuxserver/syncthing there is another box next to it, that is the tag box in there you would enter arm64-latest then click start.
      If you don't enter anything in the tag field it will just pull the latest image which is usually amd64.
      For an Odroid HC2 you've to use the tag arm32v7-latest (I've an HC1).

      kr.,
      Frepke
    • geaves wrote:

      threehappypenguins wrote:

      I have an Odroid HC2. I see in the tags stuff like "arm64,"
      I think the HC2 would be arm64-latest so when you select an image such as linuxserver/syncthing there is another box next to it, that is the tag box in there you would enter arm64-latest then click start.
      If you don't enter anything in the tag field it will just pull the latest image which is usually amd64.
      Ok, so if I have the right images, then what is going wrong?
    • gderf wrote:

      threehappypenguins wrote:

      Ok, so if I have the right images, then what is going wrong?
      Clear the log for the container, restart the container, then post the log.
      I had been deleting the containers when I'd see it wouldn't work. I added motioneye again (jshridha/motioneye latest) and I checked the log (I had no idea to do that, thanks):

      standard_init_linux.go:211: exec user process caused "exec format error"

      Also, I checked, and my Odroid HC2 has processor ARMv7 Processor rev 3 (v7l).
    • threehappypenguins wrote:

      I had been deleting the containers when I'd see it wouldn't work. I added motioneye again (jshridha/motioneye latest) and I checked the log (I had no idea to do that, thanks):
      standard_init_linux.go:211: exec user process caused "exec format error"
      That is the error you will see if you are using an incorrect image for your hardware - ie wrong tag.
      --
      Google is your friend and Bob's your uncle!

      OMV 4.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380
    • gderf wrote:

      threehappypenguins wrote:

      I had been deleting the containers when I'd see it wouldn't work. I added motioneye again (jshridha/motioneye latest) and I checked the log (I had no idea to do that, thanks):
      standard_init_linux.go:211: exec user process caused "exec format error"
      That is the error you will see if you are using an incorrect image for your hardware - ie wrong tag.
      So if none of the tags specify arm64, I can't use it? I also tried ccrisan/motioneye with 0.41-amd64 tag and I got the same error in the log. Maybe I need something different from arm64?
    • I did more Googling, and I noticed this:


      armhf stands for "arm hard float", and is the name given to a debian port for arm processors (armv7+) that have hardware floating point support.
      So I guess that I need to use the tag armhf then, since my Odroid HC2 is ARMv7 Processor rev 3 (v7l)? I haven't noticed any arm32, and not sure if that's the same thing. Also, what if it doesn't show the hardware compatibility of arm-whatever? How do I check to see what it is?
    • There is no information available for that image that mentions different tags for different hardware architectures or even what arch that image is for.

      All I can suggest is for you to find another source for an image. Try this one, but be aware there is no documentation for it:

      hub.docker.com/r/ccrisan/motioneye/
      --
      Google is your friend and Bob's your uncle!

      OMV 4.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380
    • gderf wrote:

      There is no information available for that image that mentions different tags for different hardware architectures or even what arch that image is for.

      All I can suggest is for you to find another source for an image. Try this one, but be aware there is no documentation for it:

      hub.docker.com/r/ccrisan/motioneye/
      I already tried ccrisan/motioneye with the latest image armhf as well as specifying arm64 later, and both times I got the same error in the log as all the other ones. So I guess Odroid HC2 is neither arm64 or armhf?
    • gderf wrote:

      See post # 10 above. Just be aware that specifying a tag when you pull an image does not guarantee that such an image is available. You have to look in the tag list first.
      I couldn't find anything that exactly said arm32v7, but I did find in hassioaddons/motioneye a tag that was armv7-0.5.4 so I pulled that. When I run the image, I don't get the same error as before, but now it's new:

      Brainfuck Source Code

      1. [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
      2. [s6-init] ensuring user provided files have correct perms...exited 0.
      3. [fix-attrs.d] applying ownership & permissions fixes...
      4. [fix-attrs.d] done.
      5. [cont-init.d] executing container initialization scripts...
      6. [cont-init.d] 00-banner.sh: executing...
      7. curl: (6) Could not resolve host: hassio
      8. [11:53:56] ERROR: [35mSomething went wrong contacting the API[0m
      9. [cont-init.d] 00-banner.sh: exited 0.
      10. [cont-init.d] 01-log-level.sh: executing...
      11. parse error: Invalid numeric literal at line 2, column 0
      12. parse error: Invalid numeric literal at line 2, column 0
      13. /var/run/s6/etc/cont-init.d/01-log-level.sh: line 41: log_level: unbound variable
      14. [cont-init.d] 01-log-level.sh: exited 1.
      15. [cont-finish.d] executing container finish scripts...
      16. [cont-finish.d] 99-message.sh: executing...
      17. [31m-----------------------------------------------------------[0m
      18. [31m Oops! Something went wrong.[0m
      19. [31m[0m
      20. [31m We are so sorry, but something went terribly wrong when[0m
      21. [31m starting or running this add-on.[0m
      22. [31m [0m
      23. [31m Be sure to check the log above, line by line, for hints.[0m
      24. [31m-----------------------------------------------------------[0m
      25. [cont-finish.d] 99-message.sh: exited 0.
      26. [cont-finish.d] done.
      27. [s6-finish] waiting for services.
      28. [s6-finish] sending all processes the TERM signal.
      29. [s6-finish] sending all processes the KILL signal and exiting.
      30. [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
      31. [s6-init] ensuring user provided files have correct perms...exited 0.
      32. [fix-attrs.d] applying ownership & permissions fixes...
      33. [fix-attrs.d] done.
      34. [cont-init.d] executing container initialization scripts...
      35. [cont-init.d] 00-banner.sh: executing...
      36. curl: (6) Could not resolve host: hassio
      37. [11:54:07] ERROR: [35mSomething went wrong contacting the API[0m
      38. [cont-init.d] 00-banner.sh: exited 0.
      39. [cont-init.d] 01-log-level.sh: executing...
      40. parse error: Invalid numeric literal at line 2, column 0
      41. parse error: Invalid numeric literal at line 2, column 0
      42. /var/run/s6/etc/cont-init.d/01-log-level.sh: line 41: log_level: unbound variable
      43. [cont-init.d] 01-log-level.sh: exited 1.
      44. [cont-finish.d] executing container finish scripts...
      45. [cont-finish.d] 99-message.sh: executing...
      46. [31m-----------------------------------------------------------[0m
      47. [31m Oops! Something went wrong.[0m
      48. [31m[0m
      49. [31m We are so sorry, but something went terribly wrong when[0m
      50. [31m starting or running this add-on.[0m
      51. [31m [0m
      52. [31m Be sure to check the log above, line by line, for hints.[0m
      53. [31m-----------------------------------------------------------[0m
      54. [cont-finish.d] 99-message.sh: exited 0.
      55. [cont-finish.d] done.
      56. [s6-finish] waiting for services.
      57. [s6-finish] sending all processes the TERM signal.
      58. [s6-finish] sending all processes the KILL signal and exiting.
      Display All