Ciao a tutti, ho bisogno di aiuto, non riesco a installare Pihole sul mio OMV tramite Docker compose ... Sto chiedendo aiuto, per favore allega i miei errori..
Pihole not connet
-
-
please create first the macvlan on compose webGUI and then use my pihole.yml for reference
is named MyMacVlan on my example.
-
si prega di creare prima il macvlan su compose webGUI e poi utilizzare il mio pihole.yml come riferimento
si chiama MyMacVlan nel mio esempio.
Code
Alles anzeigenImpossibile eseguire il comando 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; esportazione LANG=C.UTF-8; esportazione LANGUAGE=; docker compose --file '/srv/dev-disk-by-label-DATA/Docker/pihole/pihole.yml' --env-file '/srv/dev-disk-by-label-DATA/Docker/pihole/pihole.env' --env-file '/srv/dev-disk-by-label-DATA/Docker/global.env' up -d 2>&1': parsing /srv/dev-disk-by-label-DATA/Docker/pihole/pihole.yml: yaml: riga 12: impossibile trovare ':' previsto OMV\ExecException: Impossibile eseguire il comando 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; esportazione LANG=C.UTF-8; esportazione LANGUAGE=; docker compose --file '/srv/dev-disk-by-label-DATA/Docker/pihole/pihole.yml' --env-file '/srv/dev-disk-by-label-DATA/Docker/pihole/pihole.env' --env-file '/srv/dev-disk-by-label-DATA/Docker/global.env' up -d 2>&1': parsing /srv/dev-disk-by-label-DATA/Docker/pihole/pihole.yml: yaml: riga 12: impossibile trovare ':' previsto in /usr/share/openmediavault/engined/rpc/compose.inc:693 Traccia dello stack: #0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(620): OMVRpcServiceCompose->{closure}('/tmp/bgstatusAg...', '/tmp/bgoutputIF...') #1 /usr/share/openmediavault/engined/rpc/compose.inc(696): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure)) #2 [funzione interna]: OMVRpcServiceCompose->doCommand(Array, Array) #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array) #4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('doCommand', Array, Array) #5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Compose', 'doCommand', Array, Array, 1) #6 {principale}
-
-
post your pihole.yml file, only delete password
and post to see that you have created previosl¡y a macVLAN on webGUI named MyMacVlan , on this screenshot is not created: https://forum.openmediavault.o…t/34168-screenshot-2-png/
-
post your pihole.yml file, only delete password
and post to see that you have created previosl¡y a macVLAN on webGUI named MyMacVlan , on this screenshot is not created: https://forum.openmediavault.o…t/34168-screenshot-2-png/
I took inspiration from yours and I'll also attach the macvlan
-
Here you are
-
-
Ecco il MacVLAN
-
Ecco il MacVLAN
here is the problem you can't define:
"Subnet": "192.168.2.0/24",
"IPRange": "192.168.2.128/28",
"Gateway": "192.168.2.1"
and finally assing to pihole an IP = 192.168.2.2 because is out of range (could be 192.168.2.129 to 192.168.2.143
documentation: https://www.freecodecamp.org/e…red-cidr-de-direccion-ip/
to assing 192.168.2.2 to pihole, you need to define MyMacVlan like:
"Subnet": "192.168.2.0/24",
"IPRange": "192.168.2.1/28",
"Gateway": "192.168.2.1"
this reserve IP in the range 192.168.2.2 to 192.168.2.18
if your router for example have an IP in the range, you can reserve his IP to not use on ths range.
-
please use to atach code like your pihole.yml, I need in this way to revise you do not have tabulations that are errors in a *.yml file, to avoid this fail, copy & Paste my pihole.yml, and only change your desired values.
PD: If you use global.env in compose-plugging you can copy & Paste directly pihole.yml file without share sensitive information (like I do), only need to define variables in global.env like PUID=1001 or ConfigPath=/srv/dev-disk-by-label-DATA/config
eg:
Code
Alles anzeigen# Note: 192.168.1.xxx is an example network, you must update all these to match your own. # Thanks to http://tonylawrence.com/posts/unix/synology/free-your-synology-ports/ for your reference post # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ version: "3" services: pihole: container_name: pihole image: pihole/pihole:latest hostname: pihole domainname: $URL # <-- Update on enviromen.env file networks: MyMacVlan: # <-- MACVlan Name You need to create first in Portainer WebGUI. ipv4_address: 192.168.1.2 # <-- Update to your desired Pihole IPv4 # https://www.youtube.com/watch?v=4741-YR31fM # https://www.youtube.com/watch?v=o7nn6Tv-PAw cap_add: - NET_ADMIN # Recommended but not required (DHCP needs NET_ADMIN) 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: ADMIN_EMAIL: $email FTLCONF_LOCAL_IPV4: 192.168.1.2 # <-- Update (match ipv4_address of PiHole) VIRTUAL_HOST: pihole.$URL # <-- Update (match hostname + domainname) WEBPASSWORD: $Password2 # <-- Add password (if required) PIHOLE_DNS_: 8.8.8.8;8.8.4.4 # <-- Change by your prefered DNS service like 1.1.1.1 TZ: $TZ # <-- Your Time Zone here IPv6: "false" # Volumes store your data between container upgrades volumes: - '$ConfigPath/pihole:/etc/pihole' - '$ConfigPath/pihole/dnsmasq.d:/etc/dnsmasq.d' # https://github.com/pi-hole/docker-pi-hole#note-on-capabilities restart: unless-stopped networks: MyMacVlan: external: true
-
-
other fail:
volumes:
- /srv/dev-disk-by-label-DATA/config/pihole:/etc/pihole
- /srv/dev-disk-by-label-DATA/appdata/pihole/dnsmasq.d:/etc/dnsmasq.d
is not a real / good mount point.
you need to first create a shared folder on your DATA disk to store your dockers config and use it here.
use absolute path in global.env
a good documentation is here: https://wiki.omv-extras.org/doku.php?id=omv6:docker_in_omv
-
other fail:
volumes:
- /srv/dev-disk-by-label-DATA/config/pihole:/etc/pihole
- /srv/dev-disk-by-label-DATA/appdata/pihole/dnsmasq.d:/etc/dnsmasq.d
is not a real / good mount point.
you need to first create a shared folder on your DATA disk to store your dockers config and use it here.
use absolute path in global.env
a good documentation is here: https://wiki.omv-extras.org/doku.php?id=omv6:docker_in_omv
thank you very much now after your precious help everything works... now the only thing I want to do is that all the clients of the local network pass through pihole... do I have to set something on pihole??
-
thank you very much now after your precious help everything works... now the only thing I want to do is that all the clients of the local network pass through pihole... do I have to set something on pihole??
no, you need to configure your DHCP server to serve the pihole IP like a DNS server.
PD: You can't have 2 dhcp server, so you need to decide if use your router or pihole as dhcp server.
and remember OMV can't have pihole IP as DNS because is a service into OMV, so you can use 8.8.8.8 on OMV and pihole IP on other machines.
-
-
no, è necessario configurare il server DHCP per servire l'IP pihole come un server DNS.
PD: Non puoi avere 2 server dhcp, quindi devi decidere se usare il tuo router o pihole come server dhcp.
e ricorda che OMV non può avere PIHOLE IP come DNS perché è un servizio in OMV, quindi puoi usare 8.8.8.8 su OMV e PIHOLE IP su altre macchine.
Ok
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!