I have a few questions about version 6, since running a seconds container with nightly tag.
these have probably already been answered somewhere but I couldn't find them
will version 5 files like the databases and configs convert over automatically?
would I need to manually change anything? I think the password setting will, but do I need to change/add anything else
is there a planned release date for docker main release?
I take it there is no more information yet on the release
I need to know how smooth the transition from V5 to V6 will be, if my system reboots it will install the latest docker image, if any config files need to be changed, my network will be down
it was nearly ready in August but nothing has been said about it since
hopefully its not being release on 1st December as I have no time to prepare anything
We don't recommend automatic updates (bare metal or docker). You should use the tag 2024.07.0.
What a waste of time that was, I wanted more information on v6
I know I shouldn’t automatically update, but my docker startup script recreates the container
To whatever was last pulled, which actually won’t update now I think about it because it’s never being pulled
Anyway I wanted to know about the file conversion or whatever happens when upgrading to V6 from V5 when the full release is out
And moved to general when I want docker information
I am sorry if I offend, annoy or upset anyone, but this has been a week now
I am annoyed
I have no information other than what PromoFaux posted in August
It says it will convert the files but I have modifications in lighttpd and dnsmasq
The web redesigned might not use lighttpd for all I know, the dnsmasq config seem to have changed as they were no created in my test container
I suggest you take a bit of a break from here, or we can do that for you. Being demanding is not acceptable here.
There is no need to be dismissive of our support. We always try to give as much as we can do and frequently answer questions. In the end, everyone in the support "crew" is just a volunteer and other jobs pay our daily life. I'm sorry your question seems to have slipped through and you haven't received a comment in the last week. However, this is likely just because you put the question into the general category which is not actively monitored by us (only community-support) and nobody looking at your issue had any immediate ideas. The beta 6.0 subcategory is actively monitored by us. However, replies may take up to week even here.
To answer your questions quickly: We do as much as is possible to offer a seamless transition from v5 -> v6. However, we still don't recommend automatic updates because the process can only do as much as we have been able to test and there will - almost for sure - be obscure user configurations which require us to tweak the migration process in the first hours/days after release. So to be 100% on the safe side, you basically have two options:
pihole/pihole:nightly tag and see what happens. Just make sure to have a backup. Report anything you find that doesn't work and we will fix it for the final release. There will be litte to no difference between nightly now and the final release later. We have only a few very minor discussions going on but time is currently very limited for the core team, so even small changes can take several days/weeks to be fully discussed this timeI can already tell you that lighttpd went away as does PHP to reduce both the dependencies as well as the vulnerability overhead. It also reduces the container size quite a bit (latest v5 release is 110 MB, the v6 containers are ~ 35 MB is size). Your custom dnsmasq configuration will be kept but it may be disabled by default after migration to avoid possible configuration conflicts which would need to be sorted and prevent Pi-hole from coming back up at all after upgrading. This ensures you will be "there" when re-enabling your configuration. This to reduce "surprises" as good as possible for those still running a non-recommended auto-updating.
There is no set release date because of the reasons I have described above. Pi-hole is 100% free software, we do not have to please any investors or similar as there are none. Nobody makes a living out of Pi-hole which also gives you the good feeling that nobody is trying to get your money somehow by selling licenses or adding telemetry or ....
I am really starting to not like it here
I am a few questions about V6 that were ignored
And I would say ignoring me isn’t as well
I have trouble waiting, my patience was gone after 2 days, I am sorry about that, but I also think there should have been another update in announcements, there has been no more information on V6 for 4 months
Not one person has actually read my original post, or that is what it seems like
No I never, I put it in docker, then @DanSchaper moved it to general
I didn’t notice there was one
I don’t think that will matter much anyway as HTTPS is enabled by default
Thank you for this information
I don’t think it will actually update without me pulling it, I just remove the container and use docker run again in the script
Ok, thank you
I know, I was just excited for the new release, and it sounded nearly ready
Anyway thank you for this information, that all I wanted, but instead get told I am demanding, it was not my intention
No, not this again, I know what you mean by that, that would probably be a 7 day ban, and I would lose my mind during it
And I have had enough of them in other places
I am really sorry
I copied my V5 files to my nightly container for testing
where does "04-pihole-static-dhcp.conf" get moved to as I have some scripts that monitor it and a tag to not give a dhcp lease to devices not listed
It is not used any longer. It's content is parsed and stored in /etc/pihole/pihole.toml as dhcp.hosts. When thereafter add these lines below # Per host parameters for the DHCP server in the new file /etc/pihole/dnsmasq.conf
thank you
so that has broken my script that gets that file and the queries from the database, to see when a client was last active
can TFTP be configured in pihole.toml or is that still dnsmasq
I worked it out, you have to enable misc.etc_dnsmasq_d for that file to work
can udhcpc or whatever its called be used for PXE as it is logged under settings, system, DHCP server metrics
this is probably a question for when the main release is out
I'm not sure what you mean, could you detail it? You can use any PXE client. PXE booting needs to be defined manually through advanced dnsmasq configuration just as TFTP.
TFTP/PXE network booting, I had it setup in dnsmasq, but version 6 seems to use a separate DHCP as well as dnsmasq
under settings, system, DHCP server metrics, there is a metric called PXE, but dnsmasq TFTP does not increase that value, so it must be looking at the other DHCP server called udhcpc or something like that
it works with dnsmasq, I just want to know if the metrics can show the actual number served
when using dnsmasq for TFTP, the PXE value does not increase
does nobody know anything about the DHCP changes, the I discovered within 5 seconds of converting V5 to V6
the dnsmasq static file going into pihole.toml so I knew dnsmasq was not being used for DHCP, and found udhcpc is the /etc folder
Ever since pihole-FTL was introduced with Pi-hole v4 in 2018, dnsmasq has not been used for DHCP, but note that pihole-FTL is a tailored fork of dnsmasq using the same configuration options, except for those configuration options specific to pihole-FTL.
Your post is not quite clear, but it seems you are looking for a way to apply some custom dnsmasq configuration options you've been using with Pi-hole v5 to Pi-hole v6?
If that's the case, hasn't that been answered already?
If you need to add custom dnsmasq configuration details that are not covered by pihole.toml, you may add them as described in the aforementioned /etc/pihole/dnsmasq.conf:
# IF YOU WISH TO CHANGE ANY OF THESE VALUES, CHANGE THEM IN #
# /etc/pihole/pihole.toml #
# and restart pihole-FTL #
# #
# ANY OTHER CHANGES SHOULD BE MADE IN A SEPARATE CONFIG FILE #
# WITHIN /etc/dnsmasq.d/yourname.conf #
# (make sure misc.etc_dnsmasq_d is set to true in /etc/pihole/pihole.toml) #
how come the config was under dnsmasq for static lease then
its as clear as I can get it
there is a metric from the DHCP server called PXE
but using dnsmasq PXE with TFTP does not increase the metric
Well, because...
I knew pihole-FTL was based on dnsmasq, but thought, that run the DHCP the same as dnsmasq, as everything was exactly the same as running dnsmasq on it’s own
Least it’s more clear now in v6, so can the DHCP run TFTP without dnsmasq, so the metric works