can't bind to socket: Cannot assign requested address

[vvirtues]

Details

Related Issues

• I have searched this repository/Pi-hole forums for existing issues and pull requests that look similar

How to reproduce the issue

1. Environment data

• Operating System: Windows (Ubuntu WSL2)
• Hardware: PC
• Kernel Architecture: amd64
• Docker Install Info and version:
  • Software source: Official (Docker Desktop)
  • Supplimentary Software: n/a
• Hardware architecture: x64/86

2. docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here
   

3. any additional info to help reproduce

These common fixes didn't work for my issue

• I have tried removing/destroying my container, and re-creating a new container
• I have tried fresh volume data by backing up and moving/removing the old volume data
• I have tried running the stock docker run example(s) in the readme (removing any customizations I added)
• I have tried a newer or older version of Docker Pi-hole (depending what version the issue started in for me)
• I have tried running without my volume data mounts to eliminate volumes as the cause

If the above debugging / fixes revealed any new information note it here.
Add any other debugging steps you've taken or theories on root cause that may help.

[vvirtues]

dont think volumes are the cause, probably a windows networking/router issue

[rdwebdesign]

I think your issue is network mode host.

Docker Desktop for Windows recently introduced this mode, but I think you need to enabled it before using: https://docs.docker.com/engine/network/drivers/host/#docker-desktop

[vvirtues]

ive turned it on before, but it seems it isnt in beta anymore

[vvirtues]

note everything except the title works fine

[vvirtues]

I think your issue is network mode host.

Docker Desktop for Windows recently introduced this mode, but I think you need to enabled it before using: docs.docker.com/engine/network/drivers/host#docker-desktop

doesn't help, unfortunately

[vvirtues]

I see here on the bottom of the page

Processes inside the container cannot bind to the IP addresses of the host because the container has no direct access to the interfaces of the host

https://docs.docker.com/engine/network/drivers/host/

[vvirtues]

setting FTLCONF_LOCAL_IPV4 to 'localhost' seems to work. Ill get back later

[vvirtues]

i cant access it outside of my device (LAN doesnt work either)

[vvirtues]

i gave up on host networking. using ports regularly works fine

[PromoFaux]

I've never actually tried running a network-availble Pi-hole instance on my windows machine, I just use it for dev work.