I am using the DNS option to set my docker containers to use pihole also running in docker as their DNS. This has worked for a long time until 7.1.2. Since booting after 7.1.2, my docker containers cannot talk to pi-hole but pi-hole is working and other devices can access it.

 

Help?

nicknas2-diagnostics-20250515-2140.zip

Bump for help please

Can you describe your network config? I just posted an issue with containers on a VLAN not being able to communicate with the host.

 

Curious if this is the same problem.

1 minute ago, aglyons said:

Can you describe your network config? I just posted an issue with containers on a VLAN not being able to communicate with the host.

 

Curious if this is the same problem.

Realtek 2.5G card for Unraid, pihole setup with its own IP on the same subnet as my other devices. Other containers use shared networking

You're running pihole in a container in HOST mode or you created a custom network for PiHole? MACVLAN or IPVLAN?

3 minutes ago, aglyons said:

You're running pihole in a container in HOST mode or you created a custom network for PiHole? MACVLAN or IPVLAN?

Custom network, ipvlan

So this is the same situation I am seeing.

 

I also just came across another similar post that is showing the same problem. IMO, this is a new issue since 7.1.x was released.

 

That post does talk about the SHIM network and some scripts that need to run to solve the problem. But I have to question why this is an issue now when it wasn't before. If this is a known issue and there is a known workaround, why wasn't that workaround built into the release?

 

 

I recommend referring to this thread as it has both a discussion and a solution that is working for people.

I was able to resolve this by stopping docker, changing ipvlan to macvlan, saving then reverting and saving, and also changing host access to custom networks to disabled, saving then enabled, and saving again. Finally re-enabled docker and seem to be working again for now