Pi-hole in doker network problem

    • flmaxey wrote:

      this thread will get butchered up

      You are the author of [How To] Install Pi-Hole in Docker: Update - 08/10/18 right?

      Care to elaborate
      • why do you suggest configuring a DNS server manually (why do you think this is needed at all?)
      • why do you suggest using Google's server when it's about using Pi-Hole (do you catch the irony handing out your whole surf history to Google? Some people recommend using Cloudflare's 1.1.1.1 in the meantime but this doesn't improve things a lot)
      Are you aware that if there is no real reason to configure manually a DNS server @Nefertiti would've been up and running within minutes and not days? At least I think it's better to finish a task within minutes and without hassles than spending hours on something that requires a thread in a forum full of problematic advises (e.g. recommending to not use a well known DHCP feature called 'static allocation' the OP already successfully used)
    • tkaiser wrote:

      Care to elaborate
      No, that would be pointless and there's no point in continuing this thread.

      @ryecoaaron approved the Docker/Pi-Hole How-To and there's no reason to change it. If you feel it's technically insufficient or hurting users, by some odd stretch of imagination, take it up with him.

      I think we're done here...

      Video Guides :!: New User Guide :!: Docker Guides :!: Pi-hole in Docker
      Good backup takes the "drama" out of computing.
      ____________________________________
      Primary: OMV 3.0.99, ThinkServer TS140, 12GB ECC, 32GB USB boot, 4TB+4TB zmirror, 3TB client backup.
      Backup: OMV 4.1.13, Intel Server SC5650HCBRP, 6GB ECC, 16GB USB boot, UnionFS+SNAPRAID
      2nd Backup: OMV 4.1.9, Acer RC-111, 4GB, 32GB USB boot, 3TB+3TB zmirror, 4TB Rsync'ed disk

      The post was edited 1 time, last by flmaxey ().

    • tkaiser wrote:

      @Nefertiti: can you provide output from 'armbianmonitor -u' when you're logged into OMV on your RPi via SSH? In case you use an OMV image older than 1 year this will produce only 'command now found' but if you started with OMV 3 after July 2017 we might get some insights.
      Far from me to reopen the thread but above all the polemic witch I feel in a way l a little bit responsible Anyway here what I got from root
      root@raspberrypi:/# armbianmonitor -u
      /var/log/armhwinfo.log has been uploaded to sprunge.us/80Suyn output at drive.google.com/file/d/1m78lY…L6XZ_FVa/view?usp=sharing
      Please post the URL in the forum where you've been asked for.
      I was thinking it is possible not only I upgraded from 3.99 to 4.. but also I changed the device to a new 3b+ so maybe eth1 may come from this process Since I was never be able to install 4... from fresh On any devices even with a brand new SD

      The post was edited 2 times, last by Nefertiti ().

    • Nefertiti wrote:

      root@raspberrypi:/# armbianmonitor -u
      /var/log/armhwinfo.log has been uploaded to sprunge.us/80Suyn
      Thank you for helping to improve OMV unlike others here.

      Ok, so debug output is telling clearly that your only interface all the time was eth1 while you were able to create an eth0 entry in the GUI (which of course led to the expected result not being able to activate the non existing interface). So there's definitely some room for improvements wrt interface handling at least on the ARM images where there's no entry present after installation (due to different initial setup attempt).

      Currently no idea how to deal with this since your log shows some rename events occurring after each and every reboot:

      Source Code

      1. lan78xx 1-1.1.1:1.0 eth1: renamed from eth0
      And I also do not understand how it was possible that you were able to create an eth0 entry in the OMV UI (but I can confirm with my own testings in OMV4 on EspressoBin).

      The 'funny' part is that the interface name wouldn't be a problem at all if the tutorial you tried to follow would not recommend an extra step to create an eth0 entry to hand over all your private web activity to Google (the questions @flmaxey is either not able or willing to answer. And obviously not even willing to think about whether it's a great idea recommding Google DNS for Pi-Hole users and their privacy concerns).

      Without the 'needed' step to configure Google's DNS server (we still don't know why since the tutorial author is not able to answer simple questions) you would've been up and running in no time if you would've been aware that your interface name is eth1 and not eth0 which I consider a problem since there's a mismatch between OMV UI and reality according to ip addr.
    • Nefertiti wrote:

      /var/log/armhwinfo.log has been uploaded to sprunge.us/80Suyn

      BTW: If you look at the end of dmesg output at the bottom of the link it can be seen that there's something seriously wrong now that you've Docker running:

      Source Code

      1. [172415.683565] docker0: port 1(vethac4f4cb) entered disabled state
      2. [172415.701859] device vethac4f4cb left promiscuous mode
      3. [172415.701879] docker0: port 1(vethac4f4cb) entered disabled state
      4. [172445.919171] docker0: port 1(veth1a6b012) entered blocking state
      5. [172445.919185] docker0: port 1(veth1a6b012) entered disabled state
      6. [172445.919635] device veth1a6b012 entered promiscuous mode
      7. [172446.765454] eth0: renamed from vethd3b86dc
      8. [172446.817994] docker0: port 1(veth1a6b012) entered blocking state
      9. [172446.818011] docker0: port 1(veth1a6b012) entered forwarding state
      10. [172447.647998] docker0: port 1(veth1a6b012) entered disabled state
      11. [172447.648504] vethd3b86dc: renamed from eth0
      Display All

      (and so on -- this most probably also floods /var/log/system.log so you might run into a 'filesystem full' situation sometimes in the future)

      Update: Maybe already within the next few hours:

      Source Code

      1. ### df:
      2. Filesystem Size Used Avail Use% Mounted on
      3. ...
      4. folder2ram 489M 331M 159M 68% /var/log
    • @Nefertiti: can you please provide the output from these two commands:

      Source Code

      1. nmcli dev show
      2. ip addr
      on your device? I'm preparing a thread to discuss necessary changes in the way OMV interacts with the basic Armbian system your currently using and am about to collect information. Since your OMV box suffers from the same problem as my test machine (OMV allowing to create an eth0 interface when the interface in question is eth1 in your case) it would be great to have as much data as possible.

      BTW: I hope you're aware that something's wrong on your board as already mentioned? You might check df -h /var/log.
    • tkaiser wrote:

      @Nefertiti: can you please provide the output from these two commands:

      Source Code

      1. nmcli dev show
      2. ip addr


      on your device? I'm preparing a thread to discuss necessary changes in the way OMV interacts with the basic Armbian system your currently using and am about to collect information. Since your OMV box suffers from the same problem as my test machine (OMV allowing to create an eth0 interface when the interface in question is eth1 in your case) it would be great to have as much data as possible.

      BTW: I hope you're aware that something's wrong on your board as already mentioned? You might check df -h /var/log.

      Source Code

      1. root@raspberrypi:/# nmcli dev show
      2. GENERAL.DEVICE: docker0
      3. GENERAL.TYPE: bridge
      4. GENERAL.HWADDR: 02:42:8B:D6:7A:4D
      5. GENERAL.MTU: 1500
      6. GENERAL.STATE: 100 (connected)
      7. GENERAL.CONNECTION: docker0
      8. GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/1
      9. IP4.ADDRESS[1]: 172.17.0.1/16
      10. IP4.GATEWAY: --
      11. IP6.GATEWAY: --
      12. GENERAL.DEVICE: wlan1
      13. GENERAL.TYPE: wifi
      14. GENERAL.HWADDR: D6:68:84:7A:E1:29
      15. GENERAL.MTU: 0
      16. GENERAL.STATE: 30 (disconnected)
      17. GENERAL.CONNECTION: --
      18. GENERAL.CON-PATH: --
      19. GENERAL.DEVICE: eth1
      20. GENERAL.TYPE: ethernet
      21. GENERAL.HWADDR: B8:27:EB:9F:FC:29
      22. GENERAL.MTU: 1500
      23. GENERAL.STATE: 10 (unmanaged)
      24. GENERAL.CONNECTION: --
      25. GENERAL.CON-PATH: --
      26. WIRED-PROPERTIES.CARRIER: on
      27. IP4.ADDRESS[1]: 192.168.2.150/24
      28. IP4.GATEWAY: 192.168.2.1
      29. IP4.ROUTE[1]: dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000
      30. IP6.GATEWAY: --
      31. GENERAL.DEVICE: lo
      32. GENERAL.TYPE: loopback
      33. GENERAL.HWADDR: 00:00:00:00:00:00
      34. GENERAL.MTU: 65536
      35. GENERAL.STATE: 10 (unmanaged)
      36. GENERAL.CONNECTION: --
      37. GENERAL.CON-PATH: --
      38. IP4.ADDRESS[1]: 127.0.0.1/8
      39. IP4.GATEWAY: --
      40. IP6.ADDRESS[1]: ::1/128
      41. IP6.GATEWAY: --
      42. root@raspberrypi:/# ^C
      43. root@raspberrypi:/#
      44. root@raspberrypi:/# root@raspberrypi:/# nmcli dev show
      45. bash: root@raspberrypi:/#: No such file or directory
      46. root@raspberrypi:/# GENERAL.DEVICE: docker0
      47. bash: GENERAL.DEVICE:: command not found
      48. root@raspberrypi:/# GENERAL.TYPE: bridge
      49. bash: GENERAL.TYPE:: command not found
      50. root@raspberrypi:/# GENERAL.HWADDR: 02:42:8B:D6:7A:4D
      51. bash: GENERAL.HWADDR:: command not found
      52. root@raspberrypi:/# GENERAL.MTU: 1500
      53. bash: GENERAL.MTU:: command not found
      54. root@raspberrypi:/# GENERAL.STATE: 100 (connected)
      55. bash: syntax error near unexpected token `('
      56. root@raspberrypi:/# GENERAL.CONNECTION: docker0
      57. bash: GENERAL.CONNECTION:: command not found
      58. root@raspberrypi:/# GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/1
      59. bash: GENERAL.CON-PATH:: command not found
      60. root@raspberrypi:/# IP4.ADDRESS[1]: 172.17.0.1/16
      61. bash: IP4.ADDRESS[1]:: command not found
      62. root@raspberrypi:/# IP4.GATEWAY: --
      63. bash: IP4.GATEWAY:: command not found
      64. root@raspberrypi:/# IP6.GATEWAY: --
      65. bash: IP6.GATEWAY:: command not found
      66. root@raspberrypi:/#
      67. root@raspberrypi:/# GENERAL.DEVICE: wlan1
      68. bash: GENERAL.DEVICE:: command not found
      69. root@raspberrypi:/# GENERAL.TYPE: wifi
      70. bash: GENERAL.TYPE:: command not found
      71. root@raspberrypi:/# GENERAL.HWADDR: D6:68:84:7A:E1:29
      72. bash: GENERAL.HWADDR:: command not found
      73. root@raspberrypi:/# GENERAL.MTU: 0
      74. bash: GENERAL.MTU:: command not found
      75. root@raspberrypi:/# GENERAL.STATE: 30 (disconnected)
      76. bash: syntax error near unexpected token `('
      77. root@raspberrypi:/# GENERAL.CONNECTION: --
      78. bash: GENERAL.CONNECTION:: command not found
      79. root@raspberrypi:/# GENERAL.CON-PATH: --
      80. bash: GENERAL.CON-PATH:: command not found
      81. root@raspberrypi:/#
      82. root@raspberrypi:/# GENERAL.DEVICE: eth1
      83. bash: GENERAL.DEVICE:: command not found
      84. root@raspberrypi:/# GENERAL.TYPE: ethernet
      85. bash: GENERAL.TYPE:: command not found
      86. root@raspberrypi:/# GENERAL.HWADDR: B8:27:EB:9F:FC:29
      87. bash: GENERAL.HWADDR:: command not found
      88. root@raspberrypi:/# GENERAL.MTU: 1500
      89. bash: GENERAL.MTU:: command not found
      90. root@raspberrypi:/# GENERAL.STATE: 10 (unmanaged)
      91. bash: syntax error near unexpected token `('
      92. root@raspberrypi:/# GENERAL.CONNECTION: --
      93. bash: GENERAL.CONNECTION:: command not found
      94. root@raspberrypi:/# GENERAL.CON-PATH: --
      95. bash: GENERAL.CON-PATH:: command not found
      96. root@raspberrypi:/# WIRED-PROPERTIES.CARRIER: on
      97. bash: WIRED-PROPERTIES.CARRIER:: command not found
      98. root@raspberrypi:/# IP4.ADDRESS[1]: 192.168.2.150/24
      99. bash: IP4.ADDRESS[1]:: command not found
      100. root@raspberrypi:/# IP4.GATEWAY: 192.168.2.1
      101. bash: IP4.GATEWAY:: command not found
      102. root@raspberrypi:/# IP4.ROUTE[1]: dst = 169.254.0.0/16, nh = 0.0.0.0, mt = 1000
      103. bash: IP4.ROUTE[1]:: command not found
      104. root@raspberrypi:/# IP6.GATEWAY: --
      105. bash: IP6.GATEWAY:: command not found
      106. root@raspberrypi:/#
      107. root@raspberrypi:/# GENERAL.DEVICE: lo
      108. bash: GENERAL.DEVICE:: command not found
      109. root@raspberrypi:/# GENERAL.TYPE: loopback
      110. bash: GENERAL.TYPE:: command not found
      111. root@raspberrypi:/# GENERAL.HWADDR: 00:00:00:00:00:00
      112. bash: GENERAL.HWADDR:: command not found
      113. root@raspberrypi:/# GENERAL.MTU: 65536
      114. bash: GENERAL.MTU:: command not found
      115. root@raspberrypi:/# GENERAL.STATE: 10 (unmanaged)
      116. bash: syntax error near unexpected token `('
      117. root@raspberrypi:/# GENERAL.CONNECTION: --
      118. bash: GENERAL.CONNECTION:: command not found
      119. root@raspberrypi:/# GENERAL.CON-PATH: --
      120. bash: GENERAL.CON-PATH:: command not found
      121. root@raspberrypi:/# IP4.ADDRESS[1]: 127.0.0.1/8
      122. bash: IP4.ADDRESS[1]:: command not found
      123. root@raspberrypi:/# IP4.GATEWAY: --
      124. bash: IP4.GATEWAY:: command not found
      125. root@raspberrypi:/# IP6.ADDRESS[1]: ::1/128
      126. bash: IP6.ADDRESS[1]:: command not found
      127. root@raspberrypi:/# IP6.GATEWAY: --
      128. bash: IP6.GATEWAY:: command not found
      129. root@raspberrypi:/# ot found
      130. bash: ot: command not found
      131. root@raspberrypi:/# root@raspberrypi:/#
      132. bash: root@raspberrypi:/#: No such file or directory
      Display All

      Source Code

      1. root@raspberrypi:/# ip addr
      2. 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
      3. link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      4. inet 127.0.0.1/8 scope host lo
      5. valid_lft forever preferred_lft forever
      6. inet6 ::1/128 scope host
      7. valid_lft forever preferred_lft forever
      8. 2: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
      9. link/ether b8:27:eb:9f:fc:29 brd ff:ff:ff:ff:ff:ff
      10. inet 192.168.2.150/24 brd 192.168.2.255 scope global eth1
      11. valid_lft forever preferred_lft forever
      12. 3: wlan1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
      13. link/ether 2e:43:70:ab:5e:12 brd ff:ff:ff:ff:ff:ff
      14. 4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
      15. link/ether 02:42:8b:d6:7a:4d brd ff:ff:ff:ff:ff:ff
      16. inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
      17. valid_lft forever preferred_lft forever
      Display All
      I have no idea how to fix my board here the output any advice would be appreciated!

      root@raspberrypi:/# df -h /var/log
      Filesystem Size Used Avail Use% Mounted on
      folder2ram 489M 203M 287M 42% /var/log
    • Nefertiti wrote:

      folder2ram 489M 203M 287M 42% /var/log
      I guess you rebooted in the meantime since last time /var/log/ was filled with 331M which is way too much (folder2ram uses uncompressed RAM -- something @ryecoaaron might look into soon -- so this huge amount of logs will not only fill the partition quickly but also take away RAM from the rest of the system).

      At the end of the armbianmonitor -u output it could be seen that network devices got disabled/enabled/renamed multiple times per second. You might check with dmesg | tail -n 100 whether that's still the problem.

      I've no idea why this happens but I suspect it's due to following @'flmaxey''s tutorial and using eth0 everywhere? I would check how you created the macvlan device since if this uses eth0 instead of eth1 as parent device then clearly something's wrong. Whether this is the culprit I don't know.

      Thank you for the other output. Things start to make sense (needing unrelated fixes in OMV somewhere)
    • tkaiser wrote:

      folder2ram uses uncompressed RAM -- something @ryecoaaron might look into soon
      I still want to do that. Just haven't had a chance to look into it.
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!