Pihole docker lost config afther reboot

Help
1

Hi, i runnig fine Pihole docker on Openmedavult 7 x64 but when on upgrade contairer and reboot Pihole lost config and padsword to entrer on web admin and i must reconfigure all allways include web admin password . Any sugestion?

Best regard
Pd Excuse my rudimentary english.

2

We need more information.

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

or if you run your Pi-hole as a Docker container:

docker exec -it <pihole-container-name-or-id> pihole -d

where you substitute <pihole-container-name-or-id> as required.

3

Good mornig, i've dowloaded
pihole_debug.zip (6,7 KB)
my Pi-Hole log file and i attach it.

My docker compose config:

services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    hostname: TipiHole
    # domainname: $URL                    # <-- Update on enviromen.env file
    networks:
      Piholemacvlan:                        # <-- MACVlan Name You need to create first in Portainer WebGUI.
        ipv4_address: 192.168.1.241       # <-- Update to your desired Pihole IPv4 I use 192.168.1.2 that is free
# 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: xxxxx@gmail.com
      FTLCONF_LOCAL_IPV4: 192.168.1.241   # <-- Update (match ipv4_address of PiHole)
      # VIRTUAL_HOST: pihole.$URL    # <-- Update (match hostname + domainname)
      WEBPASSWORD: xxxxxx         # <-- Add password (if required)
      PIHOLE_DNS_: 1.0.0.1;1.1.1.1      # <-- Change by your prefered DNS service like 1.1.1.1
      TZ: Europe/Madrid                 # <-- Your Time Zone here
      IPv6: "false"
# Volumes store your data between container upgrades
    volumes:
      - /Nvme/Dockers/Pihole/etc-pihole:/etc/pihol
      - /Nvme/Dockers/Pihole/etc-dnsmasq.d:/etc/dnsmasq.d
#   https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
    restart: unless-stopped

networks:
  Piholemacvlan:
    external: true

Regards

4

See the disclaimer for the Pi-hole v6 Docker image, in particular about environment variables:

!!! THE LATEST VERSION CONTAINS BREAKING CHANGES

Pi-hole v6 has been entirely redesigned from the ground up and contains many breaking changes.

Environment variable names have changed, script locations may have changed.

If you are using volumes to persist your configuration, be careful.
Replacing any v5 image (2024.07.0 and earlier) with a v6 image will result in updated configuration files. These changes are irreversible.

Your docker compose is still using v5 environment variables.
Please have a read of Upgrading from v5.x - Pi-hole documentation and adjust as required.

5

I runnig docker on persisten volume (Nvme disk). I will trie upgade my docker.

Thanks for all

6

Good evening, I have looked at the migration document for Pi-Hole compose from v5 to v6 and I have 2 questions.

1- In my current version of docker compose I have the line:

FTLCONF_LOCAL_IPV4: 192.168.1.241", in that IP the clients were configured as dns 1 (through the router) and in the compose of the v6 version of docker I don't see it.

2- In my current version of docker compose I have network definitions....

networks:
Piholemacvlan: # <-- MACVlan Name You need to create first in Portainer WebGUI.
ipv4_address: 192.168.1.241

networks:
Piholemacvlan:
external: true

...that I don't see in docker compose v6. Not if they aren't there because it's no longer necessary.

In my local network my Pi-Hole server don´t is Dhcp server i, is my router.

Greetings

PS. I come from the Windows server world and I still have a learning curve in this.

7

From our documentation (link already posted above):

Nearly all environment variables from previous versions have been removed, but functionality can be replicated by setting their FTLCONF_ equivalent instead. (See Configuration page for more details).

If you want to replace FTLCONF_LOCAL_IPV4, try FTLCONF_dns_reply_host_IPv4

We also didn't have Piholemacvlan in our README. This is your personal configuration... a Compose file customization.
You can use any valid network in your Compose file, but they won't be in our examples.

8

Ok thanks

9

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.