You'll get little or no help with that yaml file because it is not properly formatted. Post it in a code box.
Best way to get OMV and pi-hole to play nice?
-
-
networks:
my-macvlan:
driver: macvlan
driver_opts:
parent: eth0 # network interface
ipam:
config:
- subnet: 192.168.0.0/24 # subnet ip
- gateway: 192.168.0.1 # router gateway ip
- ip_range: 192.168.0.240/29 # ip range set in dhcp on router
I hit save and tried to start it and I got the following error.
Any idea what I did wrong?
yes, that part is not necesary if you previosly created my-macvlan on compose webGUI.
And please post properly well indented yaml file on a code box.
PD: You can use the pihole.yaml file on my signature
-
Any idea what I did wrong?
As you have already been told, you must publish the file in a code box. As you have published it, not all the possible errors are visible.
If you receive an error in a red box, copy it to the clipboard in notifications and paste it into the forum in text format in a code box. Don't post a screenshot.
-
-
ya, sorry about that, I got confused and thought pressing the quote on the bottom of your reply was the method, I missed that it is at the top of the reply bar. I did copy and paste the code that was indented, but because I forgot that the code button was at the top it got reformatted.... here it is.
CodeI created a macvlan network and called it "my-macvlan" . The output of that docker network inspect i as follows: [ { "Name": "my-macvlan", "Id": "1fd9109c6e48ff4ab5e804c83b827b999bb3a2a67046d27860da890a8152eaa7", "Created": "2023-09-13T17:04:09.362587608-04:00", "Scope": "local", "Driver": "macvlan", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "192.168.0.0/24", "IPRange": "192.168.0.240/29", "Gateway": "192.168.0.1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": {}, "Options": { "parent": "eth0" }, "Labels": {} } ] END OF LINE █
Code
Display Moreversion: "3" # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ services: pihole: hostname: pihole networks: my-macvlan: # name of the macvlan network you created ipv4_address: 192.168.0.245 # the ip address you set in DHCP container_name: pihole image: pihole/pihole:latest # For DHCP it is recommended to remove these ports and instead add: network_mode: "host" ports: - "53:53/tcp" - "53:53/udp" # - "67:67/udp" # Only required if you are using Pi-hole as your DHCP server - "80:80/tcp" environment: TZ: 'America/Toronto' WEBPASSWORD: 'xxxxxxx' # set a secure password # Volumes store your data between container upgrades volumes: - './etc-pihole:/etc/pihole' - './etc-dnsmasq.d:/etc/dnsmasq.d' # https://github.com/pi-hole/docker-pi-hole#note-on-capabilities # cap_add: # - NET_ADMIN # Required if you are using Pi-hole as your DHCP server, else not needed restart: "unless-stopped" networks: my-macvlan: driver: macvlan driver_opts: parent: eth0 # network interface ipam: config: - subnet: 192.168.0.0/24 # subnet ip - gateway: 192.168.0.1 # router gateway ip - ip_range: 192.168.0.240/29 # ip range set in dhcp on router
I will leave off the last part from networks, down, I wasn't sure why it had networks twice, I was trying to follow a couple examples.
So essentially am I to infer from the indent placing of the "network" code that "networks" to the far left means create and everything more to the right means more read or access this? Is there a recommended guide on the formation of docker compose that makes it easier to understand? (webpage or video series?)
-
I have no idea where all this came from. I suppose from some procedure you found somewhere. That's another way of doing it.
There are many different ways to do things in linux. The only thing I can say is that you should choose a procedure, the one you like the most, and follow it from the beginning to the end. If it doesn't work for you, choose another one, start from scratch and follow it from the beginning to the end. If you mix some procedures with others you will not achieve anything positive.
-
I just get confused, Really frustrated might be a better word. This trying to set up pi-hole has been going on for the better part of a month now and I have be unable to get it running. I really drains me, to fail over and over again. So I guess I just become unsure, don't want to ask even more stupid sounding questions here (really it is embarrassing for me, to seem so dimwitted), so when I learn a little and fail, I read from other sources and see if changing it might help.
For example before I failed on the compose I showed (with the extra network creation at the end) I failed with out it with the following error (at the end of the red error I took a screen shot of) which speaks to my my-macvlan being undefined. That is when I searched some more and found some info (wrong in hind site) hoping to figure out how to "define" the macvlan I set up "my-macvlan". Here was my error in OMV when I tried to start it and here is the output from my creation of my macvlan network . I don't understand why it doesn't work and it is embarrassing to be have to be walked through this like a child, but here I am.
So any ideas?
Code[ { "Name": "my-macvlan", "Id": "1fd9109c6e48ff4ab5e804c83b827b999bb3a2a67046d27860da890a8152eaa7", "Created": "2023-09-13T17:04:09.362587608-04:00", "Scope": "local", "Driver": "macvlan", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "192.168.0.0/24", "IPRange": "192.168.0.240/29", "Gateway": "192.168.0.1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": {}, "Options": { "parent": "eth0" }, "Labels": {} } ] END OF LINE
Code
Display Moreversion: "3" # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ services: pihole: hostname: pihole networks: my-macvlan: # name of the macvlan network you created ipv4_address: 192.168.0.245 # the ip address you set in DHCP container_name: pihole image: pihole/pihole:latest # For DHCP it is recommended to remove these ports and instead add: network_mode: "host" ports: - "53:53/tcp" - "53:53/udp" # - "67:67/udp" # Only required if you are using Pi-hole as your DHCP server - "80:80/tcp" environment: TZ: 'America/Toronto' WEBPASSWORD: 'XXXXXX' # set a secure password # Volumes store your data between container upgrades volumes: - './etc-pihole:/etc/pihole' - './etc-dnsmasq.d:/etc/dnsmasq.d' # https://github.com/pi-hole/docker-pi-hole#note-on-capabilities # cap_add: # - NET_ADMIN # Required if you are using Pi-hole as your DHCP server, else not needed restart: "unless-stopped"
-
-
update:
I ran my problem through chatGPT.
It seems my error was that I still needed to put the second networks line in, but it needed to be formatted as follows:
Code
Display Moreversion: "3" services: pihole: hostname: pihole networks: my-macvlan: # name of the macvlan network you created ipv4_address: 192.168.0.245 # the ip address you set in DHCP container_name: pihole image: pihole/pihole:latest ports: - "53:53/tcp" - "53:53/udp" - "80:80/tcp" environment: TZ: 'America/Toronto' WEBPASSWORD: 'XXXXXXX' # set a secure password volumes: - './etc-pihole:/etc/pihole' - './etc-dnsmasq.d:/etc/dnsmasq.d' restart: "unless-stopped" networks: my-macvlan: external: true
All this for missing "external: true.
Crap.
Well another learning lesson. Sorry to bother anyone out here, I am grateful for all the help, everyone has given me.
-
update:
I ran my problem through chatGPT.
It seems my error was that I still needed to put the second networks line in, but it needed to be formatted as follows:
Code
Display Moreversion: "3" services: pihole: hostname: pihole networks: my-macvlan: # name of the macvlan network you created ipv4_address: 192.168.0.245 # the ip address you set in DHCP container_name: pihole image: pihole/pihole:latest ports: - "53:53/tcp" - "53:53/udp" - "80:80/tcp" environment: TZ: 'America/Toronto' WEBPASSWORD: 'XXXXXXX' # set a secure password volumes: - './etc-pihole:/etc/pihole' - './etc-dnsmasq.d:/etc/dnsmasq.d' restart: "unless-stopped" networks: my-macvlan: external: true
All this for missing "external: true.
Crap.
Well another learning lesson. Sorry to bother anyone out here, I am grateful for all the help, everyone has given me.
you are also missing paths to folders
-
I asked chatGPT that very question when it spat me out a docker compose... It said I could use just the ./ and it would point to the directory where docker was installed.
The ./ seems to have placed the paths in my correct directories (as far as I can tell), on my connected SSD.
Here is the output.
Code
Display More[ { "Id": "sha256:927e9854247157c40259b84b60d3e774283ba12fc91ea0feab86536320deebb1", "RepoTags": [ "pihole/pihole:latest" ], "RepoDigests": [ "pihole/pihole@sha256:8bc45afe1625487aef62859a5bf02f3d7b3429e480f4e29e4689635ab86ec312" ], "Parent": "", "Comment": "buildkit.dockerfile.v0", "Created": "2023-05-30T18:53:35.471121075Z", "Container": "", "ContainerConfig": { "Hostname": "", "Domainname": "", "User": "", "AttachStdin": false, "AttachStdout": false, "AttachStderr": false, "Tty": false, "OpenStdin": false, "StdinOnce": false, "Env": null, "Cmd": null, "Image": "", "Volumes": null, "WorkingDir": "", "Entrypoint": null, "OnBuild": null, "Labels": null }, "DockerVersion": "", "Author": "", "Config": { "Hostname": "", "Domainname": "", "User": "", "AttachStdin": false, "AttachStdout": false, "AttachStderr": false, "ExposedPorts": { "53/tcp": {}, "53/udp": {}, "67/udp": {}, "80/tcp": {} }, "Tty": false, "OpenStdin": false, "StdinOnce": false, "Env": [ "PATH=/opt/pihole:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin", "phpver=php", "PHP_ERROR_LOG=/var/log/lighttpd/error-pihole.log", "IPv6=True", "S6_KEEP_ENV=1", "S6_BEHAVIOUR_IF_STAGE2_FAILS=2", "S6_CMD_WAIT_FOR_SERVICES_MAXTIME=0", "FTLCONF_LOCAL_IPV4=0.0.0.0", "FTL_CMD=no-daemon", "DNSMASQ_USER=pihole" ], "Cmd": null, "Healthcheck": { "Test": [ "CMD-SHELL", "dig +short +norecurse +retry=0 @127.0.0.1 pi.hole || exit 1" ] }, "Image": "", "Volumes": null, "WorkingDir": "", "Entrypoint": [ "/s6-init" ], "OnBuild": null, "Labels": { "org.opencontainers.image.created": "2023-05-30T18:51:05.660Z", "org.opencontainers.image.description": "Pi-hole in a docker container", "org.opencontainers.image.licenses": "", "org.opencontainers.image.revision": "37bd3d2f0f9321211d9370fc96b7d06325cee887", "org.opencontainers.image.source": "https://github.com/pi-hole/docker-pi-hole", "org.opencontainers.image.title": "docker-pi-hole", "org.opencontainers.image.url": "https://github.com/pi-hole/docker-pi-hole", "org.opencontainers.image.version": "2023.05.2" }, "Shell": [ "/bin/bash", "-c" ] }, "Architecture": "arm64", "Os": "linux", "Size": 294132095, "VirtualSize": 294132095, "GraphDriver": { "Data": { "LowerDir": "/srv/dev-disk-by-uuid-54146848-6bf4-4006-948f-7bd05b5eb4c6/Docker/overlay2/f7ffd5c3751f9533bf5b4c7d77f946913e2be187f67fa5327e42aee6c14f3638/diff:/srv/dev-disk-by-uuid-54146848-6bf4-4006-948f-7bd05b5eb4c6/Docker/overlay2/6f35a8b4a2a3c782402bc25cda681e06b5af61c68194d9c7886940ab9ff0e857/diff:/srv/dev-disk-by-uuid-54146848-6bf4-4006-948f-7bd05b5eb4c6/Docker/overlay2/6e0cc1f6f4651d81267d22159989377e0ec5dbc75f33a66d2ba98b4b56f41f90/diff:/srv/dev-disk-by-uuid-54146848-6bf4-4006-948f-7bd05b5eb4c6/Docker/overlay2/ab2511ab67a541d3c8766c27347f884cdf8932d4cdef6cf179583e9965df48b4/diff:/srv/dev-disk-by-uuid-54146848-6bf4-4006-948f-7bd05b5eb4c6/Docker/overlay2/987cccca73bb6f662bb38250f5d92986b30db6c93a04106948da38d0385a4f76/diff:/srv/dev-disk-by-uuid-54146848-6bf4-4006-948f-7bd05b5eb4c6/Docker/overlay2/78ea2748ba4104f31de758aa72c0b753dedff5e645f6d226ec39aaa253e1698a/diff:/srv/dev-disk-by-uuid-54146848-6bf4-4006-948f-7bd05b5eb4c6/Docker/overlay2/99891e95182412c104f141cba7b2df09341dea95fee98ac92cebb987ac4cfde3/diff:/srv/dev-disk-by-uuid-54146848-6bf4-4006-948f-7bd05b5eb4c6/Docker/overlay2/05e44dbc072c9ac38a7427960a2d736997dde728bba1bb09bb1a23535f15c14e/diff", "MergedDir": "/srv/dev-disk-by-uuid-54146848-6bf4-4006-948f-7bd05b5eb4c6/Docker/overlay2/b1db8d28256d32e7ff0644bd4698f7b4c7dc684b80e016c6daa6a8ddd1ec5e69/merged", "UpperDir": "/srv/dev-disk-by-uuid-54146848-6bf4-4006-948f-7bd05b5eb4c6/Docker/overlay2/b1db8d28256d32e7ff0644bd4698f7b4c7dc684b80e016c6daa6a8ddd1ec5e69/diff", "WorkDir": "/srv/dev-disk-by-uuid-54146848-6bf4-4006-948f-7bd05b5eb4c6/Docker/overlay2/b1db8d28256d32e7ff0644bd4698f7b4c7dc684b80e016c6daa6a8ddd1ec5e69/work" }, "Name": "overlay2" }, "RootFS": { "Type": "layers", "Layers": [ "sha256:13594e6f72105befed183626c2e1c6d7b31d7fc2c0f7e682d7fb5f2a75e5c4a2", "sha256:1bb4d946ceef7f5945db4a3ff7f91a8f0b5fe6239aad5d3f0c8bf57f8b740419", "sha256:5f70bf18a086007016e948b04aed3b82103a36bea41755b6cddfaf10ace3c6ef", "sha256:c53f5e4695ba3b1fd4ead7d8d9c59f8bae89c750225f5308a933827cae7bbed0", "sha256:885da28193e4b57e9c54daed0c4f256fecf77d0df42074c4931f2ddf73c6df3a", "sha256:94e3a0d3cddb22e5891a76ea27a8ed66ab4d175acea8a9178000f299b51a1fe2", "sha256:aa50ba4cf51d72db2d67c185e049f55e78b607f365ce012219d8ffe5b802e3ca", "sha256:5fdc734eff9bebc508dae778b6be76e8276c512bd88262d03ea1940792b0bb27", "sha256:0728cfff109aac5580d49dfc7cbeb59fd1646dc6c46a5c89dd173168a2f0557b" ] }, "Metadata": { "LastTagTime": "0001-01-01T00:00:00Z" } } ] END OF LINE
It is running, but in your opinion is it not correct or flawed?
-
-
I ran my problem through chatGPT.
It seems my error was that I still needed to put the second networks line in, but it needed to be formatted as follows:You had the answer that chatgpt gave you in the first procedure I gave you. Here: https://wiki.omv-extras.org/do…_interface_in_a_container
You just had to follow the procedure until the end.
The ./ seems to have placed the paths in my correct directories (as far as I can tell), on my connected SSD.
Those are relative paths and it is correct. Those folders will be created in the folder you have defined in Services>Compose>Settings in the Compose Files Section, as explained here. https://wiki.omv-extras.org/do…-compose_with_the_plug-in
-
I asked chatGPT that very question when it spat me out a docker compose.
Don't use shatGPT than.
-
Sadly, I failed again, not sure what I did wrong...
I created a macvlan network and called it "my-macvlan" . The output of that docker network inspect i as follows:
[ { "Name": "my-macvlan", "Id": "1fd9109c6e48ff4ab5e804c83b827b999bb3a2a67046d27860da890a8152eaa7", "Created": "2023-09-13T17:04:09.362587608-04:00", "Scope": "local", "Driver": "macvlan", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "192.168.0.0/24", "IPRange": "192.168.0.240/29", "Gateway": "192.168.0.1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": {}, "Options": { "parent": "eth0" }, "Labels": {} }
]END OF LINE
█
I then worked on a docker compose with my information found out a few messages above. (wasn't sure if I was supposed to allow pihole to be my dhcp server so i #'ed it out.)
version: "3"
# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/
services:
pihole:
hostname: pihole
networks:
my-macvlan: # name of the macvlan network you created
ipv4_address: 192.168.0.245 # the ip address you set in DHCP
container_name: pihole
image: pihole/pihole:latest
# For DHCP it is recommended to remove these ports and instead add: network_mode: "host"
ports:
- "53:53/tcp"
- "53:53/udp"
# - "67:67/udp" # Only required if you are using Pi-hole as your DHCP server
- "80:80/tcp"
environment:
TZ: 'America/Toronto'
WEBPASSWORD: 'Freedom52' # set a secure password
# Volumes store your data between container upgrades
volumes:
- './etc-pihole:/etc/pihole'
- './etc-dnsmasq.d:/etc/dnsmasq.d'
# https://github.com/pi-hole/doc…hole#note-on-capabilities
# cap_add:
# - NET_ADMIN # Required if you are using Pi-hole as your DHCP server, else not needed
https://casinosanalyzer.com/bonuses-by-countries/ireland-irl makes me sure when
playing due to its reviews about free spins at the best Irish no deposit casino.restart: "unless-stopped"
networks:
my-macvlan:
driver: macvlan
driver_opts:
parent: eth0 # network interface
ipam:
config:
- subnet: 192.168.0.0/24 # subnet ip
- gateway: 192.168.0.1 # router gateway ip
- ip_range: 192.168.0.240/29 # ip range set in dhcp on router
I hit save and tried to start it and I got the following error.
Any idea what I did wrong?
Are you using Docker Compose to manage any other containers on your system? If so, are you having any trouble with those containers? Because I do and Idk how to manage this...
Any feedback will be appreciated. -
-
Hi can you help me?
this is my stack
Code
Display Moreversion: "3" services: pihole: hostname: pihole networks: macvlan_NET: ipv4_address: 192.168.1.10 container_name: pihole image: pihole/pihole:latest ports: - 53:53/tcp - 53:53/udp - 6080:80/tcp environment: - TZ=Europe/Rome - WEBPASSWORD=password volumes: - /srv/dev-disk-by-uuid-60eb5dee-5512-498c-b33d-dfbc7415f017/appdata/pihole/etc-pihole:/etc/pihole - /srv/dev-disk-by-uuid-60eb5dee-5512-498c-b33d-dfbc7415f017/appdata/pihole/etc-dnsmasq.d:/etc/dnsmasq.d restart: unless-stopped networks: macvlan_NET: driver: macvlan driver_opts: parent: enp1s0 ipam: config: - subnet: 192.168.1.10/24 gateway: 192.168.1.1 ip_range: 192.168.1.10/32
The log:
[i] Starting docker specific checks & setup for docker pihole/pihole
[i] Setting capabilities on pihole-FTL where possible
[i] Applying the following caps to pihole-FTL:
* CAP_CHOWN
* CAP_NET_BIND_SERVICE
* CAP_NET_RAW
[i] Ensuring basic configuration by re-running select functions from basic-install.sh
[i] Installing configs from /etc/.pihole...
[i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone!
[i] Installing /etc/dnsmasq.d/01-pihole.conf...
[✓] Installed /etc/dnsmasq.d/01-pihole.conf
[i] Installing /etc/.pihole/advanced/06-rfc6761.conf...
[✓] Installed /etc/dnsmasq.d/06-rfc6761.conf
[i] Installing latest logrotate script...
[✓] Installing latest logrotate script
[i] Creating empty /etc/pihole/setupVars.conf file.
[i] Assigning password defined by Environment Variable
[✓] New password set
[i] Added ENV to php:
"TZ" => "Europe/Rome",
"PIHOLE_DOCKER_TAG" => "",
"PHP_ERROR_LOG" => "/var/log/lighttpd/error-pihole.log",
"CORS_HOSTS" => "",
"VIRTUAL_HOST" => "pihole",
[i] Using IPv4 and IPv6
[i] Installing latest Cron script...
[✓] Installing latest Cron script
[i] setup_blocklists now setting default blocklists up:
[i] TIP: Use a docker volume for /etc/pihole/adlists.list if you want to customize for first boot
[i] Blocklists (/etc/pihole/adlists.list) now set to:
https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
[i] Configuring default DNS servers: 8.8.8.8, 8.8.4.4
[i] Applying pihole-FTL.conf setting LOCAL_IPV4=0.0.0.0
[i] FTL binding to default interface: eth0
[i] Enabling Query Logging
[i] Testing lighttpd config: Syntax OK
[i] All config checks passed, cleared for startup ...
[i] Docker start setup complete
[i] pihole-FTL (no-daemon) will be started as pihole
s6-rc: info: service _startup successfully started
s6-rc: info: service pihole-FTL: starting
s6-rc: info: service pihole-FTL successfully started
s6-rc: info: service lighttpd: starting
s6-rc: info: service lighttpd successfully started
s6-rc: info: service _postFTL: starting
Checking if custom gravity.db is set in /etc/pihole/pihole-FTL.conf
s6-rc: info: service _postFTL successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[i] Creating new gravity database
[i] Migrating content of /etc/pihole/adlists.list into new database
[i] Neutrino emissions detected...
[✓] Pulling blocklist source list into range
[i] Preparing new gravity database...
[✓] Preparing new gravity database
[i] Creating new gravity databases...
[✓] Creating new gravity databases
[i] Using libz compression
[i] Target: https://raw.githubusercontent.…nBlack/hosts/master/hosts
[i] Status: Pending...
[✓] Status: Retrieval successful
[✓] Parsed 144136 exact domains and 0 ABP-style domains (ignored 1 non-domain entries)
Sample of non-domain entries:
- "0.0.0.0"
[i] Building tree...
[✓] Building tree
[i] Swapping databases...
[✓] Swapping databases
[✓] The old database remains available
[i] Number of gravity domains: 144136 (144136 unique domains)
[i] Number of exact blacklisted domains: 0
[i] Number of regex blacklist filters: 0
[i] Number of exact whitelisted domains: 0
[i] Number of regex whitelist filters: 0
/bin/bash: line 1: 266 Hangup /usr/bin/pihole-FTL no-daemon > /dev/null 2>&1
[i] Cleaning up stray matter...
[✓] Cleaning up stray matter
Stopping pihole-FTL
pihole-FTL: no process found
[✓] FTL is listening on port
[✓] UDP (IPv4)
[✓] TCP (IPv4)
[✗] UDP (IPv6)
[✓] TCP (IPv6)
[i] Pi-hole blocking will be enabled
[i] Enabling blocking
[✓] Pi-hole Enabled
/bin/bash: line 1: 402 Real-time signal 0 /usr/bin/pihole-FTL no-daemon > /dev/null 2>&1
Stopping pihole-FTL
pihole-FTL: no process found
fatal: unable to access 'https://github.com/pi-hole/pi-hole/': Could not resolve host: github.com
fatal: unable to access 'https://github.com/pi-hole/web/': Could not resolve host: github.com
fatal: unable to access 'https://github.com/pi-hole/FTL/': Could not resolve host: github.com
Pi-hole version is v5.17.2 (Latest: N/A)
web version is v5.21 (Latest: v5.21)
FTL version is v5.23 (Latest: N/A)
Container tag is: 2023.11.0
What i wrong? Thanx
-
I have a doubt..... pardon ..mmm this "app" is only for raspberry? I have OMV installed on a normal PC.
-
- subnet: 192.168.1.10/24
Possibly this is the error. I think it should be:
- subnet: 192.168.1.0/24
Anyway, here is a procedure to do this that I would say is simpler. https://wiki.omv-extras.org/do…_the_same_lan_as_the_host
this "app" is only for raspberry?
No, it is not only for raspberry. It is a docker container, unless that container is created for arm architecture it should work on your PC. Pihole works on amd64 architecture too.
-
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!