New user, WSL/docker on Win10 help

First time user of Docker (edit: on Windows 10 with WSL2) and Pihole here so forgive. I pulled pihole with

docker run --name=pihole -e TZ=America/El_Salvador -e WEBPASSWORD=xx -e ServerIP=192.168.0.100 -v pihole_app:/etc/pihole -v dns_config:/etc/dnsmasq.d -p 5000:80 -p 53:53/tcp -p 53:53/udp --restart=unless-stopped pihole/pihole:2021.12.1

It installs and seems to filter, except PiHole network interfaces show IP scheme not related to my network, and doesn't reflect above ServerIP. Eth0 shows 172.17.0.1, and there's an unused 'if' interface along with the loopback. I get the alert

Client 172.17.0.1 has been rate-limited (current config allows up to 1000 queries in 60 seconds)

and Query Logs show only this address for any/all clients' activity.

I can ping pi.hole from my windows host and returns as my same local IP. /etc/pihole/local.list is empty and nslookup returns yet another address scheme don't use

# nslookup
> msn.com
Server:         192.168.65.5
Address:        192.168.65.5#53

Non-authoritative answer:
Name:   msn.com
Address: 13.82.28.61
> wind
Server:         192.168.65.5
Address:        192.168.65.5#53

edit: I found the 192.168.65.5 in docker gui network settings, but not sure how this should go at this point. Also hostname in GUI shows as the container ID and I can not ping that. Conditional forwarding is configured.

Depending on your chosen Docker network mode, it is expected that Docker would isolate a container into a separate network, usually within the 172.16.0.0/12 range.

In your case, I'd guess you'd be using one of Docker's bridge network modes, where traffic would be NATed, so all traffic would originate from Docker's routing 172.17.0.1.

Note that for Docker on Windows, available network modes and capabilities would be limited when compared to Docker on Linux - consult Docker's documentation for further details.