Docker-Anfänger-Problem mit Konfiguration des Netzwerkes -> Docker beginner problem with network configuration

    • OMV 4.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Docker-Anfänger-Problem mit Konfiguration des Netzwerkes -> Docker beginner problem with network configuration

      Hallo alle,
      bitte gebt mir einige Hinweise, wie das Netzwerk richtig zu konfigurieren ist, damit ich auf den Kodi-Container zugreifen kann, denn hier kommen immer Fehler hoch:

      Hello, everybody,

      please give me some hints on how to configure the network correctly, so that I can access the Kodi container, because there are always errors:



      Vielen Dank schon jetzt und freundliche Grüße.

      Thank you very much and kind regards.
    • The IP from my OMV is 192.168.115.130, it is a banana pi.

      Source Code

      1. login as: root
      2. root@192.168.115.130's password:
      3. ____ ____ _
      4. | __ ) __ _ _ __ __ _ _ __ __ _ | _ \(_)
      5. | _ \ / _` | '_ \ / _` | '_ \ / _` | | |_) | |
      6. | |_) | (_| | | | | (_| | | | | (_| | | __/| |
      7. |____/ \__,_|_| |_|\__,_|_| |_|\__,_| |_| |_|
      8. Welcome to ARMBIAN 5.70 stable Debian GNU/Linux 9 (stretch) 4.19.13-sunxi
      9. System load: 0.25 0.39 0.36 Up time: 41 min
      10. Memory usage: 16 % of 998MB IP: 192.168.115.130
      11. CPU temp: 40°C
      12. Usage of /: 99% of 7.4G storage/: 63% of 466G
      13. [ General system configuration (beta): armbian-config ]
      14. Last login: Mon Jan 14 11:07:29 2019 from 192.168.115.3
      15. root@bananapi:~# ifconfig
      16. docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
      17. inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
      18. ether 02:42:04:89:a1:64 txqueuelen 0 (Ethernet)
      19. RX packets 0 bytes 0 (0.0 B)
      20. RX errors 0 dropped 0 overruns 0 frame 0
      21. TX packets 0 bytes 0 (0.0 B)
      22. TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
      23. eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
      24. inet 192.168.115.130 netmask 255.255.255.0 broadcast 192.168.115.255
      25. inet6 2003:f8:93d2:2700:8536:5d97:7278:497 prefixlen 64 scopeid 0x0<global>
      26. inet6 2003:f8:93d2:2700:6952:243:479e:6f19 prefixlen 64 scopeid 0x0<global>
      27. inet6 fe80::3a8f:6d60:602e:ae5d prefixlen 64 scopeid 0x20<link>
      28. ether 02:ca:08:02:de:d3 txqueuelen 1000 (Ethernet)
      29. RX packets 9788 bytes 2161128 (2.0 MiB)
      30. RX errors 0 dropped 4 overruns 0 frame 0
      31. TX packets 2160 bytes 645893 (630.7 KiB)
      32. TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
      33. device interrupt 60
      34. lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
      35. inet 127.0.0.1 netmask 255.0.0.0
      36. inet6 ::1 prefixlen 128 scopeid 0x10<host>
      37. loop txqueuelen 1000 (Lokale Schleife)
      38. RX packets 814 bytes 92382 (90.2 KiB)
      39. RX errors 0 dropped 0 overruns 0 frame 0
      40. TX packets 814 bytes 92382 (90.2 KiB)
      41. TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
      42. root@bananapi:~#
      Display All


      Wenn ich eine neue Netzwerkschnittstelle hinzufügen will (eth0) kommen neue Fehler hoch.
      Gibt es bitte weitere Hinweise?

      When I want to add a new network interface (eth0), new errors come up.
      Any other leads, please?
    • omv-firstaid displayed error while I selected option 1:

      Source Code

      1. ERROR: dialog-like terminated due to an error: the dialog-like program exited with status 3 (which was passed to it as the DIALOG_ERROR environment variable). Sometimes, the reason is simply that dialog was given a height or width parameter that is too big for the terminal in use. Its output, with leading and trailing whitespace stripped, was:
      2. Error: Expected at least 5 tokens for --menu, have 4.
      3. Use --help to list options.
      4. root@bananapi:~#
    • omavoss wrote:

      Where I find this image lsioarmhf/kodi-headless for that BananaPi?
      When you use the search option in Docker and you type in kodi the first on the list is the one you have installed, usually the first one to appear is for amd64 (64 bit OS) scrolling down the list you'll find lsioarmhf/kodi-headless specific for arm boards.

      Say for instance you installed Heimdall Docker, in the tag section (when you select it from the search option) you would have to enter arm64v8-latest to get the correct version installed for the BananaPi.

      If your Kodi is running and it works and you don't get constant restarts or any other errors then leave it.
      Raid is not a backup! Would you go skydiving without a parachute?