Hi, I am facing a problem - I am running a graylog multicontainer image created with docker-compose in WSL running in Hyper-V virtual. I have portforwarded necessary ports plus SMTP. Graylog application runs fine and is accessible throught host and LAN. It is connected to default bridge network with IP like (172.17.X.X) and my created bridge network. Our LAN uses 192.168.3.X subnet with GW running on 192.168.3.2. My bridge network has 192.168.3.0/24 subnet and container can ping GW (with just the default network). But I cannot access any other LAN address from container as it looks like the created network is not used at all. Docker Desktop network is default 192.168.65.1. Firewall if off on host. When trying to ping address in the same 3.X subnet I get “No route to host” error. What I am trying to achieve is getting email alerts from Graylog to work.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Createing a bridge network | 3 | 13774 | March 21, 2022 | |
| Docker Compose bridge networks don't work in WSL2 on Windows | 12 | 380 | July 12, 2025 | |
| Host networking not working on Docker Desktop in WSL2 with mirrored mode | 3 | 1245 | June 5, 2025 | |
| Use bridge networking instead of NAT in Docker Desktop on Windows | 6 | 290 | May 15, 2025 | |
| WSL 2 and port forwarding | 5 | 29522 | February 19, 2025 |