Windows docker container cannot reach another host on the same private network

us flag

I'm running a Docker container on Windows:

docker run -d -p 2001:8080
-v F:\Scan:/app/data/output
--restart unless-stopped
--name scanservjs

This basically helps converting my Scanner into a Wifi Scanner.

I confirm is definitely accessible (a raspberry pi on the same private network), and from the Host (Windows), I can ping and telnet 6566 without any issues.

This was definitely working before, but for some reason (maybe due to Windows updates or so), my container no longer seems to be able to reach at all. If I install ping on the container, ping just hangs forever.

I've tried a number of things, such as trying some network settings (converting to docker-compose.yml and add some network settings, etc), but couldn't get anything to work so far. I tried --net=host, but then I don't seem to be able to access localhost:2001 or localhost:8080, so I was unable to do much.

I tried to temp disable Windows Firewall, but doesn't seem to resolve either.

Windows host -> raspberry pi [good]  
Docker container (in Windows host) -> raspberry pi [fail]

What could be the problem that prevents the Docker container from reaching, while the Windows host can without any problems?


Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.