iamstoxe / wirehole Goto Github PK

I have made a docker compose file based on this as follows (urls etc changed for obvious reasons).

version: "3"

networks:
  private_network:
    ipam:
      driver: default
      config:
        - subnet: 10.2.0.0/24

services:
  wireguard:
    depends_on: [pihole]
    image: linuxserver/wireguard
    container_name: wireguard
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London # Change to your timezone
      - SERVERPORT=51820
      - SERVERURL=testvpn.test.com #optional - For use with DDNS (Uncomment to use)
      - PEERS=2 # How many peers to generate for you (clients)
      - PEERDNS=10.2.0.100 # Set it to point to pihole
      - INTERNAL_SUBNET=10.6.0.0
    volumes:
      - ./wireguard:/config
      - /lib/modules:/lib/modules
    ports:
      - "51820:51820/udp"
    dns:
      - 10.2.0.100 # Points to pihole
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1
    restart: unless-stopped
    networks:
      private_network:
        ipv4_address: 10.2.0.3

  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    restart: unless-stopped
    hostname: pihole
    dns:
      - 127.0.0.1
    environment:
      TZ: "Europe/London"
      WEBPASSWORD: "testpassword" # Blank password - Can be whatever you want.
      ServerIP: 10.1.0.100
      DNS1: 1.1.1.1
      DNS2: 1.1.1.1 # If we don't specify two, it will auto pick google.
    volumes:
      - "./etc-pihole/:/etc/pihole/"
      - "./etc-dnsmasq.d/:/etc/dnsmasq.d/"
    # Recommended but not required (DHCP needs NET_ADMIN)
    #   https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
    cap_add:
      - NET_ADMIN
    networks:
      private_network:
        ipv4_address: 10.2.0.100

This works really well and I am able to get on to the wireguard vpn and have access (though have lost seeing different clients in pi hole compared to running native).

I have tried to remove the INTERNAL_SUBNET environment variable from the wireguard service as on dockerhub for wireguard it says its optional and this defaults it to 10.13.13.0 which I thought would be acceptable however only removing that breaks the whole thing. Was hoping someone could help me understand why.

Thanks in advance.

How do you upgrade when new releases of PiHole, Wireguard, etc become available?

Absolutely in love with this docker-compose setup. I'm really kind of a n00b with docker and docker-compose and learning along the way and so happy this more or less works right out of the box. The only thing I wish we could do using this config set up is be able to pass along each of the WG client IPs over through pihole so that I can manage groups and whitelist certain domains for different devices, etc. Is this at all possible with this kind of set up?

Hi, i'm looking for help.
I think there is an error in the unbound configuration but i have not the skills to fix it.
Both unbound and pihole are listening to the same port 53 and unbound can't work.
I found in pihole guide instructions to modify the unbound port to 5335 (https://docs.pi-hole.net/guides/dns/unbound/) but files and directories aren't the same so i don't know where i can change it.
Can anyone help me please?
Thank you :)

Hi all,
First, thanks for your work, it's a really smart solution,

I enconter a problem with allowedips list, in my docker-compose i got :
- ALLOWEDIPS=10.6.0.2/32,192.168.22.0/24

When the container go up, in logs :
**** AllowedIPs for peers 10.6.0.2/32,192.168.22.0/24 ****

But, in the container, when i drop the tj conf :

root@5591ebbed6cd:/# wg
interface: wg0
  public key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx=
  private key: (hidden)
  listening port: 51820

peer: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx=
  allowed ips: 10.6.0.2/32

The only way i found is to add manually after creation with :
wg set wg0 peer xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx= allowed-ips 10.6.0.2/32,192.168.22.0/24

Best regards ;-)

hi man,
thanks for this awesome project but here I am having an issue.
This is probably on my part but I'm unable to get docker-compose working.
I have search multiple sites (stack overflow, etc) and none of the solutions has worked.

executed the following commands to see if docker / compose was correctly installed.
docker version docker-compose -version(here is the first error) if I just execute docker-compose I get this error:/usr/local/bin/docker-compose: line 1: Not: command not found`

can you help me at least to get docker-compose working?

(** No kernel headers found in the Ubuntu or Debian repos!! Will try the headers from host (if mapped), may or may not work ****
wireguard | **** Kernel headers don't seem to be available, can't compile the module. Sleeping now. . . ****) anyone knows how to convert it for centos ? the only deference the installation process its yum instead of apt

I am trying to get this setup on rpi and have updated the docker image for unbound to use "mvance/unbound-rpi:latest" because I ran into issues during the setup.

unbound:
    image: "mvance/unbound-rpi:latest"
    container_name: unbound
    restart: unless-stopped
    hostname: "unbound"
    privileged: true
    volumes:
      - "./unbound:/opt/unbound/etc/unbound/"
    networks:
      private_network:
        ipv4_address: 10.2.0.200

During the setup I see the following errors:

unbound      | [1629602752] libunbound[18:0] error: udp connect failed: Cannot assign requested address for 2001:503:ba3e::2:30 port 53
unbound      | [1629602752] libunbound[18:0] error: udp connect failed: Cannot assign requested address for 2001:500:a8::e port 53
unbound      | [1629602752] libunbound[18:0] error: udp connect failed: Cannot assign requested address for 2001:503:ba3e::2:30 port 53
unbound      | [1629602753] libunbound[18:0] error: udp connect failed: Cannot assign requested address for 2001:500:1::53 port 53
unbound      | [1629602753] libunbound[18:0] error: udp connect failed: Cannot assign requested address for 2001:7fd::1 port 53
unbound      | /opt/unbound/etc/unbound/unbound.conf:293: error: cannot open include file '/opt/unbound/etc/unbound/a-records.conf': No such file or directory
unbound      | /opt/unbound/etc/unbound/unbound.conf:294: error: cannot open include file '/opt/unbound/etc/unbound/srv-records.conf': No such file or directory
unbound      | /opt/unbound/etc/unbound/unbound.conf:300: error: cannot open include file '/opt/unbound/etc/unbound/forward-records.conf': No such file or directory
unbound      | read /opt/unbound/etc/unbound/unbound.conf failed: 3 errors in configuration file
unbound      | [1629602753] unbound[1:0] fatal error: Could not read config file: /opt/unbound/etc/unbound/unbound.conf. Maybe try unbound -dd, it stays on the commandline to see more errors, or unbound-checkconf
unbound exited with code 1

I am not sure what to do to work around this. Any help would be great!

I configured my home region as San Jose because it was geographically closest to my location. Setting the region to us-sanjose-1 returns the following error:

Error: Invalid index

  on main.tf line 120, in resource "oci_core_instance" "wirehole_instance":
 120:     source_id   = var.instance_image_ocid[var.region]
    |----------------
    | var.instance_image_ocid is map of string with 24 elements
    | var.region is "us-sanjose-1"

The given key does not identify an element in this collection value.

Switching the region to "us-phoenix-1" returns a 401 error:

Error: Service error:NotAuthenticated. The required information to complete authentication was not provided or was incorrect.. http status code: 401. Opc request id: {removed}, The service for this resource encountered an error. Please contact support for help with that service

  on main.tf line 139, in data "oci_identity_availability_domain" "ad":
 139: data "oci_identity_availability_domain" "ad" {

I have created 3 peers but every time I cannot connect more than 2 clients at the same time. Also, pi-hole dashboard always show 2 clients only. Is this a bug or something wrong on my end?

Hi There,

I'm running into an issue after initiating docker-compose up. The QR code will display and it appears that pi-hole and WireGuard are working but unbound is reading a couple errors. The first one states "unbound | standard_init_linux.go:228: exec user process caused: exec format error". The second error that pops up is "unbound | standard_init_linux.go:228: exec user process caused: exec format error and continues infinitely."

I have setup Wirehole on a DigitalOcean vps and I have two clients, my Manjaro Linux laptop and my android phone. I use KDE Connect to share data and clipboard between them over wifi. While I am connected to Wirehole the two devices cannot see each other. I there a way around this?

Thanks for this great project, I just gave to it the 1000th star. 🤘

I have one question: I am already having a working wg setup on my server and I would like to keep that. I would like to use wirehole, without Wireguard.

Can I get a little help with that?

WG config is simple as:

$ sudo cat /etc/wireguard/wg0.conf
[Interface]
Address = 192.168.9.1/24
ListenPort = 51820
PrivateKey = 
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE
[Peer]
PublicKey = 
AllowedIPs = 192.168.9.2/32
[Peer]
PublicKey =
AllowedIPs = 192.168.9.3/32

I removed Wireguard part from the docker-compose.yml:

version: "3"

networks:
  private_network:
    ipam:
      driver: default
      config:
        - subnet: 10.2.0.0/24

services:
  unbound:
    image: "mvance/unbound:latest"
    container_name: unbound
    restart: unless-stopped
    hostname: "unbound"
    volumes:
      - "./unbound:/opt/unbound/etc/unbound/"
    networks:
      private_network:
        ipv4_address: 10.2.0.200

  pihole:
    depends_on: [unbound]
    container_name: pihole
    image: pihole/pihole:latest
    restart: unless-stopped
    hostname: pihole
    dns:
      - 127.0.0.1
      - 10.2.0.200 # Points to unbound
    environment:
      TZ: "America/Los_Angeles"
      WEBPASSWORD: "" # Blank password - Can be whatever you want.
      ServerIP: 10.1.0.100 # Internal IP of pihole
      DNS1: 10.2.0.200 # Unbound IP
      DNS2: 10.2.0.200 # If we don't specify two, it will auto pick google.
    # Volumes store your data between container upgrades
    volumes:
      - "./etc-pihole/:/etc/pihole/"
      - "./etc-dnsmasq.d/:/etc/dnsmasq.d/"
    # Recommended but not required (DHCP needs NET_ADMIN)
    #   https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
    cap_add:
      - NET_ADMIN
    networks:
      private_network:
        ipv4_address: 10.2.0.100

I am not a Docker expert, and I am unsure how to change IP addresses in the config above.

I think ServerIP should be WG's interface IP: 192.168.9.1, but what for the rest (subnet and 10.2.0.100 in the config)?

Thank you,
Adrian

Is there any option to restrict PiHole to WireGuard traffic only? Specifically, so that running it has no impact on other processes on the server.

pi@PiDNS:/wirehole/wirehole $ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
OK
pi@PiDNS:/wirehole/wirehole $
pi@PiDNS:~/wirehole/wirehole $ sudo add-apt-repository \

"deb [arch=amd64] https://download.docker.com/linux/ubuntu \
    $(lsb_release -cs) \
    stable" &&
sudo apt-get update &&
sudo apt-get install docker-ce docker-ce-cli containerd.io -yqq

Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 95, in
sp = SoftwareProperties(options=options)
File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 109, in init
self.reload_sourceslist()
File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 599, in reload_sourceslist
self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in get_sources
(self.id, self.codename))
aptsources.distro.NoDistroTemplateException: Error: could not find a distribution template for Raspbian/buster

Hello i have linode ubuntu 20.04. Since installing wirehole docker i am not able to apt-get update the system, it just wont connect. How to fix it?

Thank you

after creating 10 peers, is it possible to delete a specific peer? or disable it.

Great work on this!
Would love to have instructions on how to configure clients properly, as the services are running in docker containers.
I'm seeing an error that says "Handshake did not complete after 5 seconds". I scanned the QR code that's shown during setup.

I am getting this error message after using your docker compose on synology nas:

root@skyl:# docker run --rm --entrypoint unbound-anchor mvance/unbound -v
[1623525383] libunbound[1:0] error: udp connect failed: Cannot assign requested address for 2001:7fe::53 port 53
[1623525384] libunbound[1:0] error: udp connect failed: Cannot assign requested address for 2001:500:200::b port 53
/opt/unbound/etc/unbound/root.key does not exist
success: the anchor is ok

I am using your unbound.conf file.
Any help will be appreciated.
Many thanks.

I am trying to installing this on a respberry pi 3, but the image fails to work, seemingly because of unbound. I get the following error that continuously repeats.

unbound | standard_init_linux.go:207: exec user process caused "exec format error"

wireguard attempts to install its requirements but cannot resolve any domains

Installing on Ubuntu 20.04.

Error that occurs reads
unbound | /opt/unbound/sbin/unbound-anchor: error while loading shared libraries: libnghttp2.so.14: cannot open shared object file: No such file or directory

Repeats several times before
unbound exited with code 127

Then switches to pihole

  [✗] DNS resolution is not available
pihole       | [cont-init.d] 20-start.sh: exited 1.
pihole       | [cont-finish.d] executing container finish scripts...
pihole       | [cont-finish.d] done.
pihole       | [s6-finish] waiting for services.
pihole       | [s6-finish] sending all processes the TERM signal.
pihole       | [s6-finish] sending all processes the KILL signal and exiting.
pihole exited with code 1
pihole       | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
pihole       | [s6-init] ensuring user provided files have correct perms...exited 0.
pihole       | [fix-attrs.d] applying ownership & permissions fixes...
pihole       | [fix-attrs.d] 01-resolver-resolv: applying... 
pihole       | [fix-attrs.d] 01-resolver-resolv: exited 0.
pihole       | [fix-attrs.d] done.
pihole       | [cont-init.d] executing container initialization scripts...
pihole       | [cont-init.d] 20-start.sh: executing... 
pihole       |  ::: Starting docker specific checks & setup for docker pihole/pihole
unbound      | /opt/unbound/sbin/unbound-anchor: error while loading shared libraries: libnghttp2.so.14: cannot open shared object file: No such file or directory
unbound      | /opt/unbound/sbin/unbound: error while loading shared libraries: libnghttp2.so.14: cannot open shared object file: No such file or directory
unbound exited with code 127
  [✓] Update local cache of available packages
pihole       |   [i] Existing PHP installation detected : PHP version 7.0.33-0+deb9u8
pihole       | 
pihole       |   [i] Installing configs from /etc/.pihole...
pihole       |   [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
  [✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf
pihole       | chown: cannot access '': No such file or directory
pihole       | chmod: cannot access '': No such file or directory
pihole       | chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory
pihole       | ::: Pre existing WEBPASSWORD found
pihole       | Docker DNS variables not used
pihole       | Existing DNS servers used (10.2.0.200 & 10.2.0.200)
pihole       | DNSMasq binding to default interface: eth0
pihole       | Added ENV to php:
pihole       | 			"PHP_ERROR_LOG" => "/var/log/lighttpd/error.log",
pihole       | 			"ServerIP" => "10.1.0.100",
pihole       | 			"VIRTUAL_HOST" => "10.1.0.100",
pihole       | Using IPv4 and IPv6
pihole       | ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early))
pihole       | https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
pihole       | https://mirror1.malwaredomains.com/files/justdomains
pihole       | ::: Testing pihole-FTL DNS: FTL started!
pihole       | ::: Testing lighttpd config: Syntax OK
pihole       | ::: All config checks passed, cleared for startup ...
pihole       |  ::: Docker start setup complete
pihole       |   [✗] DNS resolution is currently unavailable

Process repeats many times until

unbound exited with code 127
^CGracefully stopping... (press Ctrl+C again to force)
Stopping wireguard ... done
Stopping pihole    ... done
Stopping unbound   ... done

Would appear I'm missing libnghttp2.so.14?
Should this be part of the wirehole package, or do I need to install separately? If I need to install, can you offer any guidance?

Thank you.

What values to change to customize or personalize my wireguard port or IP address?

Just by changing the port breaks wirehole and also just the INTERNAL_SUBNET also breaks wirehole

pihole -up dont work inside docker.

howto update wirehole's pihole then?

First, I want to thank you Stoxe for this amazing piece of work. Now, I would like to run all my Portainer containers through wirehole and ca't figure out how to set it up.

is there quick way to create additional users after setup?

Thank you very much for the application. Everything works well. One question is, should I configure a firewall for my security? I rented a VPS and installed ubuntu 20.04 on it and then followed your instructions. thanks

i've been sitting here for hours trying to get this to work.

Processor: BCM2711
Distribution: Raspbian GNU/Linux 10 (buster)
Kernel version: Linux 5.10.17-v7l+ armv7l
Firmware: #1421

Error:
unbound exited with code 1
unbound | standard_init_linux.go:228: exec user process caused: exec format error

Also the tipp to map other volumes to wireguard volumes did not the trick.
Tipp with Updated Kernel versions - no success

Any ideas?

I don't believe this is as much an "issue" as it is a configuration problem on my part. I have setup wirehole on a VPS and it is humming along nicely. I installed a shadowsocks server on the same VPS and it seems to be working fine also. I would like to use wirehole as DNS resolver for shadowsocks to get the benefits of adblocking and dnssec when using shadowsocks and not attached to the wirehole VPN. The shadowsocks config has an option to specify a local resolver. I have tried 127.0.0.1, 127.0.0.53 and localhost but none of these work as expected (127.0.0.53:53 is bad syntax). When using shadowsocks by itself with wirehole as DNS I do not get adblocking and dnssec. When I use full tunnel wirehole/unbound VPN and use shadowsocks as SOCKS5 proxy I do not get adblocking and secure DNS.

Is the configuration I want possible with wirehole? Is there is a config in wirehole that prevents other services on the same server from using pihole/unbound as their resolver?

I must say thank you for the excellent work. Following the guide, https://iamstoxe.com/posts/how-to-setup-a-free-pi-hole-and-wireguard-vpn-server-in-the-cloud-for-free/ got me into using cloud based VPS and it is still running as my backup VPN. You made me realise the value, flexibility and ease of use of a VPS for those who don't have sysadmin level of knowledge.

Failing during execution docker-compose up -d with error:

wireguard    | make: Leaving directory '/app/wireguard-linux-compat/src'
wireguard    | **** Let's test our new module. ****
wireguard    | **** The module is not active, review the logs. Sleeping now. . . ****
wireguard    | RTNETLINK answers: Operation not supported

System info:

Linux 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) x86_64 GNU/Linux

Please, explain how to resole that)

Do we need to setup it only on oracle? Or Can we setup it on any CloudServer such as Digital Ocean or Vultr?

A "What is this?" section at the top of the README would be helpful for people who discover this from a link and need some context

i got issues with linode to install that shell on ubuntu 16.04 @MohamedElashri probably with IP private part with pihole and unbound can you help me solve it or where to edit ip or something? thank you very much

why does the docker compose file set the ServerIP environment variable in the pihole configuration to 10.1.0.100 (ServerIP: 10.1.0.100 # Internal IP of pihole, line 67)? Shouldn't this value be set to 10.2.0.100? Also can you explain the purpose of this variable? The official pi-hole documentation on this subject is lacking at best and the default value they use is 127.0.0.1 (pi-hole itself). under what circumstances would you not point directly back to pi-hole? I am having a very difficult time coming up with a plausible reason for using 10.1.0.100 ... Thank you

Hey Stoxe, great work on this automated process!

I'm wondering if you plan on supporting Raspbian with your script? Thanks

Hi. I love what you've done so far. Tho I'd like to see a ui added for the wireguard configs. Gw-ui seems like a good option to me. Any chance it will be added?

Hello and thank you all, I've managed to create new peers for my laptop and desktop. How do I download the config files (since Desktop WireGuard doesn't use QR codes). Thank you!

Hi,

Last step of script fails on new installation of Ubuntu server 20.04 LTS.

username@wirehole:~/wirehole$ docker-compose up
ERROR: Couldn't connect to Docker daemon - you might need to run `docker-machine start default`.

And then:

username@wirehole:~/wirehole$ docker-machine start default
Docker machine "default" does not exist. Use "docker-machine ls" to list machines. Use "docker-machine create" to add a new one.

username@wirehole:~/wirehole$ docker-machine ls
NAME   ACTIVE   DRIVER   STATE   URL   SWARM   DOCKER   ERRORS

username@wirehole:~/wirehole$

Docker version

username@wirehole:~/wirehole$ sudo docker version

Client: Docker Engine - Community
 Version:           20.10.6
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        370c289
 Built:             Fri Apr  9 22:47:17 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.6
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       8728dd2
  Built:            Fri Apr  9 22:45:28 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.6
  GitCommit:        d71fcd7d8303cbf684402823e425e9dd2e99285d
 runc:
  Version:          1.0.0-rc95
  GitCommit:        b9ee9c6314599f1b4a7f497e1f1f856fe433d3b7
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Service

username@wirehole:~/wirehole$ sudo service docker status

● docker.service - Docker Application Container Engine
     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2021-05-28 07:01:05 UTC; 56min ago
TriggeredBy: ● docker.socket
       Docs: https://docs.docker.com
   Main PID: 7609 (dockerd)
      Tasks: 10
     Memory: 40.3M
     CGroup: /system.slice/docker.service
             └─7609 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock

I am not versioned with docker, so.. I tried with both original "docker-compose.yml" and edited (changed IP addresses) - I don't know if it's needed or not, so I tried :)

BR

I am running a Raspberry Pi 3B+ with a fresh installation of Raspberry Pi OS Lite (May 2021 image). I installed Docker using the convenience script posted on the official Docker website, then installed the pre-requisites as documented in the wirehole documentation.

When running docker-compose up, I see a string of log messages about unbound, then pihole, then wireguard - all of which look like they're successful.

A few seconds later, I see 'unbound exited with code 1' followed by a few dozen lines:

standard_init_linux.go:228: exec user process caused: exec format error

Eventually, I see 'unbound exited with code 1' again. Then the cycle repeats.

I tried purging the containers and images, then running again. I killed the docker-compose session again.

Then manually started unbound + wireguard. Both appear to start successfully, but then pihole hangs on start.

Here's the console output:

pi@pihole:~/github/wirehole $ sudo docker-compose up
Pulling unbound (mvance/unbound:latest)...
latest: Pulling from mvance/unbound
4c25b3090c26: Pull complete56dadb3d8df1: Pull complete47f4b691a026: Pull complete68b17be29c9e: Pull complete3a95e1173d9b: Pull completed73afc8b903c: Pull complete4f4fb700ef54: Pull completeDigest: sha256:9645c740f76cfe7bda4c327be068a2532e9c38517340be5a803a7aaf9d28ffbe
Status: Downloaded newer image for mvance/unbound:latest
Pulling pihole (pihole/pihole:latest)...
latest: Pulling from pihole/pihole
d407cd38f681: Pull completeb99820d21f60: Pull completefad45ca92af1: Pull complete81e7f2b9f135: Pull complete88133101f450: Pull completed02719cc4327: Pull complete6ec874e6abc0: Pull complete2d0049258316: Pull completeDigest: sha256:b51628bfa49b71ce4af4831b34e276693a6d647b82037151d8eb0d34da504432
Status: Downloaded newer image for pihole/pihole:latest
Pulling wireguard (linuxserver/wireguard:)...
latest: Pulling from linuxserver/wireguard
89866b708492: Pull complete11e356aa40c5: Pull complete004dd11d87c9: Pull complete082a41c5a043: Pull completeda5988138422: Pull complete712f60e26541: Pull complete6dff8de69cb6: Pull complete048f3ab18d60: Pull completeeaadb8c6cf69: Pull completeDigest: sha256:b3080bda504b053ff209c7d22764c471b8a3b1659a33a7b3ceab54343118187f
Status: Downloaded newer image for linuxserver/wireguard:latest
Creating unbound ... done
Creating pihole ... done
Creating wireguard ... done
Attaching to unbound, pihole, wireguard
unbound | standard_init_linux.go:228: exec user process caused: exec format error
pihole | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
pihole | [s6-init] ensuring user provided files have correct perms...exited 0.
pihole | [fix-attrs.d] applying ownership & permissions fixes...
pihole | [fix-attrs.d] 01-resolver-resolv: applying...
pihole | [fix-attrs.d] 01-resolver-resolv: exited 0.
pihole | [fix-attrs.d] done.
pihole | [cont-init.d] executing container initialization scripts...
pihole | [cont-init.d] 20-start.sh: executing...
pihole | ::: Starting docker specific checks & setup for docker pihole/pihole
wireguard | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
wireguard | [s6-init] ensuring user provided files have correct perms...exited 0.
wireguard | [fix-attrs.d] applying ownership & permissions fixes...
wireguard | [fix-attrs.d] done.
wireguard | [cont-init.d] executing container initialization scripts...
wireguard | [cont-init.d] 01-envfile: executing...
wireguard | [cont-init.d] 01-envfile: exited 0.
wireguard | [cont-init.d] 10-adduser: executing...
wireguard |
wireguard | -------------------------------------
wireguard | _ ()
wireguard | | | ___ _ __
wireguard | | | / | | | / \
wireguard | | | _ \ | | | () |
wireguard | || |/ || _/
wireguard |
wireguard |
wireguard | Brought to you by linuxserver.io
wireguard | -------------------------------------
wireguard |
wireguard | To support the app dev(s) visit:
wireguard | WireGuard: https://www.wireguard.com/donations/
wireguard |
wireguard | To support LSIO projects visit:
wireguard | https://www.linuxserver.io/donate/
wireguard | -------------------------------------
wireguard | GID/UID
wireguard | -------------------------------------
wireguard |
wireguard | User uid: 1000
wireguard | User gid: 1000
wireguard | -------------------------------------
wireguard |
wireguard | [cont-init.d] 10-adduser: exited 0.
wireguard | [cont-init.d] 30-config: executing...
wireguard | Uname info: Linux 526ee3a4b211 5.10.52-v7+ #1441 SMP Tue Aug 3 18:10:09 BST 2021 armv7l armv7l armv7l GNU/Linux
pihole |
pihole | [i] Installing configs from /etc/.pihole...
pihole | [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
[✓] Copying 01-pihole.conf to /etc/dnsmasq.d/01-pihole.conf
wireguard | **** It seems the wireguard module is already active. Skipping kernel header install and module compilation. ****
wireguard | **** Server mode is selected ****
pihole | Converting DNS1 to PIHOLE_DNS
pihole | Converting DNS2 to PIHOLE_DNS_
pihole | Setting DNS servers based on PIHOLE_DNS_ variable
pihole | ::: Pre existing WEBPASSWORD found
pihole | DNSMasq binding to default interface: eth0
pihole | Added ENV to php:
pihole | "PHP_ERROR_LOG" => "/var/log/lighttpd/error.log",
pihole | "ServerIP" => "10.1.0.100",
pihole | "CORS_HOSTS" => "",
pihole | "VIRTUAL_HOST" => "10.1.0.100",
pihole | Using IPv4 and IPv6
pihole | ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early))
pihole | https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
unbound exited with code 1
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
pihole | ::: Testing pihole-FTL DNS: FTL started!
pihole | ::: Testing lighttpd config: Syntax OK
pihole | ::: All config checks passed, cleared for startup ...
pihole | ::: Enabling Query Logging
pihole | [i] Enabling logging...
[✓] Logging has been enabled!
pihole | ::: Docker start setup complete
pihole | Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
pihole | Current Pi-hole version is v5.3.1.
pihole | Current AdminLTE version is v5.5.1.
pihole | Current FTL version is v5.8.1.
pihole | [cont-init.d] 20-start.sh: exited 0.
pihole | [cont-init.d] done.
pihole | [services.d] starting services
pihole | Starting lighttpd
pihole | Starting pihole-FTL (no-daemon) as root
pihole | Starting crond
pihole | [services.d] done.
unbound exited with code 1
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound exited with code 1
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
wireguard | **** SERVERURL var is either not set or is set to "auto", setting external IP to auto detected value of ****
wireguard | **** External server port is set to 47111. Make sure that port is properly forwarded to port 51820 inside this container ****
wireguard | **** Internal subnet is set to 10.6.0.0 ****
wireguard | **** AllowedIPs for peers 0.0.0.0/0, ::/0 ****
wireguard | **** Peer DNS servers will be set to 10.2.0.100 ****
wireguard | **** Server mode is selected ****
wireguard | **** Server related environment variables changed, regenerating 1 server and 1 peer/client confs ****
wireguard | PEER 1 QR code:
wireguard | █████████████████████████████████████████████████████████████████
wireguard | wireguard |

<>

█████████████████████████████████████████████████████████████████
wireguard | [cont-init.d] 30-config: exited 0.
wireguard | [cont-init.d] 90-custom-folders: executing...
wireguard | [cont-init.d] 90-custom-folders: exited 0.
wireguard | [cont-init.d] 99-custom-scripts: executing...
wireguard | [custom-init] no custom files found exiting...
wireguard | [cont-init.d] 99-custom-scripts: exited 0.
wireguard | [cont-init.d] done.
wireguard | [services.d] starting services
wireguard | [services.d] done.
wireguard | Another service is using port 53, disabling CoreDNS
wireguard | [#] ip link add wg0 type wireguard
wireguard | [#] wg setconf wg0 /dev/fd/63
wireguard | [#] ip -4 address add 10.6.0.1 dev wg0
wireguard | [#] ip link set mtu 1420 up dev wg0
wireguard | [#] ip -4 route add 10.6.0.2/32 dev wg0
wireguard | [#] iptables -A FORWARD -i wg0 -j ACCEPT; iptables -A FORWARD -o wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
unbound exited with code 1
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound exited with code 1
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound exited with code 1
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound exited with code 1
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound exited with code 1
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound exited with code 1
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound exited with code 1
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound exited with code 1
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound exited with code 1
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error
unbound | standard_init_linux.go:228: exec user process caused: exec format error

Is it possible to view all the client connected ? It is showing only single client in the dashboard

Would be possible to use pihole in my local network without connecting to wireguard?

Because in my lan, I cannot access to the IP address pihole has (10.2.0.100), it is in another subnet (I am using 192.168.X.X) and I am not sure what changes should I made in order to use pihole both, in my local network, and in Internet when using wirehole.

Thanks.

Starting unbound ... error

ERROR: for unbound  Cannot start service unbound: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: Running hook #0:: error running hook: exit status 2, stdout: , stderr: fatal error: runtime: out of memory

runtime stack:
runtime.throw(0x55fe03314e6d, 0x16)
	/usr/local/go/src/runtime/panic.go:774 +0x74 fp=0x7ffce5c3be58 sp=0x7ffce5c3be28 pc=0x55fe017485a4
runtime.sysMap(0xc000000000, 0x4000000, 0x55fe058ebb98)
	/usr/local/go/src/runtime/mem_linux.go:169 +0xc7 fp=0x7ffce5c3be98 sp=0x7ffce5c3be58 pc=0x55fe017312f7
runtime.(*mheap).sysAlloc(0x55fe058cf280, 0x2000, 0x0, 0x0)
	/usr/local/go/src/runtime/malloc.go:701 +0x1cf fp=0x7ffce5c3bf40 sp=0x7ffce5c3be98 pc=0x55fe0172428f
runtime.(*mheap).grow(0x55fe058cf280, 0x1, 0xffffffff)
	/usr/local/go/src/runtime/mheap.go:1255 +0xa5 fp=0x7ffce5c3bf90 sp=0x7ffce5c3bf40 pc=0x55fe0173f495
runtime.(*mheap).allocSpanLocked(0x55fe058cf280, 0x1, 0x55fe058ebba8, 0x1)
	/usr/local/go/src/runtime/mheap.go:1170 +0x268 fp=0x7ffce5c3c010 sp=0x7ffce5c3bf90 pc=0x55fe0173f328
runtime.(*mheap).alloc_m(0x55fe058cf280, 0x1, 0x55fe0177002a, 0x0)
	/usr/local/go/src/runtime/mheap.go:1022 +0xc6 fp=0x7ffce5c3c060 sp=0x7ffce5c3c010 pc=0x55fe0173ebc6
runtime.(*mheap).alloc.func1()
	/usr/local/go/src/runtime/mheap.go:1093 +0x4e fp=0x7ffce5c3c098 sp=0x7ffce5c3c060 pc=0x55fe017748fe
runtime.(*mheap).alloc(0x55fe058cf280, 0x1, 0x1002a, 0x40000)
	/usr/local/go/src/runtime/mheap.go:1092 +0x8c fp=0x7ffce5c3c0e8 sp=0x7ffce5c3c098 pc=0x55fe0173eeac
runtime.(*mcentral).grow(0x55fe058d00b8, 0x0)
	/usr/local/go/src/runtime/mcentral.go:255 +0x7d fp=0x7ffce5c3c128 sp=0x7ffce5c3c0e8 pc=0x55fe01730d1d
runtime.(*mcentral).cacheSpan(0x55fe058d00b8, 0x7fbf7f995000)
	/usr/local/go/src/runtime/mcentral.go:106 +0x300 fp=0x7ffce5c3c188 sp=0x7ffce5c3c128 pc=0x55fe01730840
runtime.(*mcache).refill(0x7fbf7f995008, 0x2a)
	/usr/local/go/src/runtime/mcache.go:138 +0x87 fp=0x7ffce5c3c1a8 sp=0x7ffce5c3c188 pc=0x55fe017302d7
runtime.(*mcache).nextFree(0x7fbf7f995008, 0x55fe058ebb2a, 0x7fbf7f995008, 0x8, 0xfffffffffffffff8)
	/usr/local/go/src/runtime/malloc.go:854 +0x89 fp=0x7ffce5c3c1e0 sp=0x7ffce5c3c1a8 pc=0x55fe01724ab9
runtime.mallocgc(0x180, 0x55fe04435b80, 0x1, 0x55fe058ebc00)
	/usr/local/go/src/runtime/malloc.go:1022 +0x7a5 fp=0x7ffce5c3c280 sp=0x7ffce5c3c1e0 pc=0x55fe01725405
runtime.newobject(0x55fe04435b80, 0x4000)
	/usr/local/go/src/runtime/malloc.go:1151 +0x3a fp=0x7ffce5c3c2b0 sp=0x7ffce5c3c280 pc=0x55fe0172580a
runtime.malg(0x1f05300008000, 0x55fe058d1928)
	/usr/local/go/src/runtime/proc.go:3238 +0x33 fp=0x7ffce5c3c2f0 sp=0x7ffce5c3c2b0 pc=0x55fe01751b33
runtime.mpreinit(...)
	/usr/local/go/src/runtime/os_linux.go:324
runtime.mcommoninit(0x55fe058c9d40)
	/usr/local/go/src/runtime/proc.go:626 +0xc6 fp=0x7ffce5c3c328 sp=0x7ffce5c3c2f0 pc=0x55fe0174b366
runtime.schedinit()
	/usr/local/go/src/runtime/proc.go:543 +0x76 fp=0x7ffce5c3c380 sp=0x7ffce5c3c328 pc=0x55fe0174afc6
runtime.rt0_go(0x7ffce5c3c488, 0x4, 0x7ffce5c3c488, 0x0, 0x7fbf8003709b, 0x0, 0x7ffce5c3c488, 0x4e5c3c400, 0x55fe01776cc0, 0x0, ...)
	/usr/local/go/src/runtime/asm_amd64.s:214 +0x129 fp=0x7ffce5c3c388 sp=0x7ffce5c3c380 pc=0x55fe01776df9: unknown

ERROR: for unbound  Cannot start service unbound: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: Running hook #0:: error running hook: exit status 2, stdout: , stderr: fatal error: runtime: out of memory

runtime stack:
runtime.throw(0x55fe03314e6d, 0x16)
	/usr/local/go/src/runtime/panic.go:774 +0x74 fp=0x7ffce5c3be58 sp=0x7ffce5c3be28 pc=0x55fe017485a4
runtime.sysMap(0xc000000000, 0x4000000, 0x55fe058ebb98)
	/usr/local/go/src/runtime/mem_linux.go:169 +0xc7 fp=0x7ffce5c3be98 sp=0x7ffce5c3be58 pc=0x55fe017312f7
runtime.(*mheap).sysAlloc(0x55fe058cf280, 0x2000, 0x0, 0x0)
	/usr/local/go/src/runtime/malloc.go:701 +0x1cf fp=0x7ffce5c3bf40 sp=0x7ffce5c3be98 pc=0x55fe0172428f
runtime.(*mheap).grow(0x55fe058cf280, 0x1, 0xffffffff)
	/usr/local/go/src/runtime/mheap.go:1255 +0xa5 fp=0x7ffce5c3bf90 sp=0x7ffce5c3bf40 pc=0x55fe0173f495
runtime.(*mheap).allocSpanLocked(0x55fe058cf280, 0x1, 0x55fe058ebba8, 0x1)
	/usr/local/go/src/runtime/mheap.go:1170 +0x268 fp=0x7ffce5c3c010 sp=0x7ffce5c3bf90 pc=0x55fe0173f328
runtime.(*mheap).alloc_m(0x55fe058cf280, 0x1, 0x55fe0177002a, 0x0)
	/usr/local/go/src/runtime/mheap.go:1022 +0xc6 fp=0x7ffce5c3c060 sp=0x7ffce5c3c010 pc=0x55fe0173ebc6
runtime.(*mheap).alloc.func1()
	/usr/local/go/src/runtime/mheap.go:1093 +0x4e fp=0x7ffce5c3c098 sp=0x7ffce5c3c060 pc=0x55fe017748fe
runtime.(*mheap).alloc(0x55fe058cf280, 0x1, 0x1002a, 0x40000)
	/usr/local/go/src/runtime/mheap.go:1092 +0x8c fp=0x7ffce5c3c0e8 sp=0x7ffce5c3c098 pc=0x55fe0173eeac
runtime.(*mcentral).grow(0x55fe058d00b8, 0x0)
	/usr/local/go/src/runtime/mcentral.go:255 +0x7d fp=0x7ffce5c3c128 sp=0x7ffce5c3c0e8 pc=0x55fe01730d1d
runtime.(*mcentral).cacheSpan(0x55fe058d00b8, 0x7fbf7f995000)
	/usr/local/go/src/runtime/mcentral.go:106 +0x300 fp=0x7ffce5c3c188 sp=0x7ffce5c3c128 pc=0x55fe01730840
runtime.(*mcache).refill(0x7fbf7f995008, 0x2a)
	/usr/local/go/src/runtime/mcache.go:138 +0x87 fp=0x7ffce5c3c1a8 sp=0x7ffce5c3c188 pc=0x55fe017302d7
runtime.(*mcache).nextFree(0x7fbf7f995008, 0x55fe058ebb2a, 0x7fbf7f995008, 0x8, 0xfffffffffffffff8)
	/usr/local/go/src/runtime/malloc.go:854 +0x89 fp=0x7ffce5c3c1e0 sp=0x7ffce5c3c1a8 pc=0x55fe01724ab9
runtime.mallocgc(0x180, 0x55fe04435b80, 0x1, 0x55fe058ebc00)
	/usr/local/go/src/runtime/malloc.go:1022 +0x7a5 fp=0x7ffce5c3c280 sp=0x7ffce5c3c1e0 pc=0x55fe01725405
runtime.newobject(0x55fe04435b80, 0x4000)
	/usr/local/go/src/runtime/malloc.go:1151 +0x3a fp=0x7ffce5c3c2b0 sp=0x7ffce5c3c280 pc=0x55fe0172580a
runtime.malg(0x1f05300008000, 0x55fe058d1928)
	/usr/local/go/src/runtime/proc.go:3238 +0x33 fp=0x7ffce5c3c2f0 sp=0x7ffce5c3c2b0 pc=0x55fe01751b33
runtime.mpreinit(...)
	/usr/local/go/src/runtime/os_linux.go:324
runtime.mcommoninit(0x55fe058c9d40)
	/usr/local/go/src/runtime/proc.go:626 +0xc6 fp=0x7ffce5c3c328 sp=0x7ffce5c3c2f0 pc=0x55fe0174b366
runtime.schedinit()
	/usr/local/go/src/runtime/proc.go:543 +0x76 fp=0x7ffce5c3c380 sp=0x7ffce5c3c328 pc=0x55fe0174afc6
runtime.rt0_go(0x7ffce5c3c488, 0x4, 0x7ffce5c3c488, 0x0, 0x7fbf8003709b, 0x0, 0x7ffce5c3c488, 0x4e5c3c400, 0x55fe01776cc0, 0x0, ...)
	/usr/local/go/src/runtime/asm_amd64.s:214 +0x129 fp=0x7ffce5c3c388 sp=0x7ffce5c3c380 pc=0x55fe01776df9: unknown
ERROR: Encountered errors while bringing up the project.

i just use "docker system prune -a" to start again, but what's happen?

I have setup the wirehole on an amazon VPC. While I am able to connect to to the instance, I still see my old IP when I goto whatsmyip.org even though the pihole dashboard is accessible and adblocking seems to be working.

How can I get my server's IP?

I need help Im trying to install on ARM instance

following fullsetup I installed
docker for arm
docker-compose arm using linuxserver's
and for unbound, mvance doesnt support arm64
upon looking I found klutchell's unbound so I use it
upon running docker-compose up, I got this error
anyone can help to make it work?
Thanks

According to the changelog for Pihole here: https://pi-hole.net/2021/09/11/pi-hole-ftl-v5-9-web-v5-6-and-core-v5-4-released

It states that now:

Interface-dependent handling of pi.hole and the machine’s hostname
This makes FTL automatically reply with the appropriate IP address to both pi.hole and the machines hostname. Before this change, FTL always used a hard-coded address set during the weekly gravity updates (pihole -g). The new method is interface-aware and may reply with different addresses on different interfaces (e.g. Ethernet, WiFi or Wireguard network). The address FTL replies with can be overwritten using the REPLY_ADDR4/6 settings in /etc/pihole/pihole-FTL.conf.

Obviously, overwriting the address from 10.1.0.100 in ../etc-pihole/pihole-FTL.conf doesn't work since it will get overwritten when the docker-compose runs the container. Even though I have pi.hole defined in the Local DNS for 10.2.0.100, the order in which the system resolves the address is defined by the value in pihole-FTL.conf first.

Any ideas on how to get this resolved? I'd prefer not having to enter the 10.2.0.100 address for the WebGUI.

I am trying to add a gitea service to the docker-compose.yml:

  gitea:
    image: gitea/gitea:1.15.2
    container_name: gitea
    environment:
      - USER_UID=1000
      - USER_GID=1000
    restart: always
    networks:
      - gitea
    volumes:
      - ./gitea:/data
      - /etc/timezone:/etc/timezone:ro
      - /etc/localtime:/etc/localtime:ro
    ports:
      - "3000:3000"
      - "222:22"  
    networks:
      private_network: 
        ipv4_address: 10.2.0.10

However, the container refuses to connect.

What changes to this setup do I need to make if I already have a PiHole server running located at a different IP? Would I need to change the .yml file DNS config to match my already setup PiHole? Have it running on a Raspberry Pi.

Hey!

Is there also an installation-script without Docker? or isn't that going to be working?