Open KarthiAru opened 4 months ago
These are the tricks I was doing for the Docker VMs (Windows/macOS), but I haven't tried them in years (I work on Linux). Maybe this has changed.
Let me know if you find a way to fix this on Windows 11. A first thing you could try would be to run a simple Linux image in a docker container, check the network setup and see how you can e.g. ping the Windows host.
Also, is Docker still running in a VM on Windows? Or do they somehow leverage WSL?
These are the tricks I was doing for the Docker VMs (Windows/macOS), but I haven't tried them in years (I work on Linux). Maybe this has changed.
Let me know if you find a way to fix this on Windows 11. A first thing you could try would be to run a simple Linux image in a docker container, check the network setup and see how you can e.g. ping the Windows host.
Also, is Docker still running in a VM on Windows? Or do they somehow leverage WSL?
Docker Desktop v4.31.1 (latest) uses WSL2 based engine by default. I spun up a Ubuntu container and was able to ping the host from the container. Also I was able to send and receive UDP message from the container to the host.
Sending a UDP packet from Docker container
root@docker-desktop:/# echo "Hello QGC" | nc -u 192.168.0.138 14550
Listening for UDP packet from host
PS C:\Users\karth\Documents> python test.py
received message: Hello QGC
from ('192.168.0.138', 63447)
test.py
import socket
sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
sock.bind(('0.0.0.0', 14550))
while True:
data, addr = sock.recvfrom(1024)
print("received message:", data.decode(), "from", addr)
Does this mean that 192.168.0.138 is the IP of the host from WSL? In that case did you try the following?
docker run --rm -it jonasvautherin/px4-gazebo-headless:1.14.3 192.168.0.138 192.168.0.138
Try downgrading to Docker Desktop 4.30.0, it worked for me
Hi,
The MAVLink traffic for UDP port 14550 (and 14540) does not seem to arrive in QGroundControl (and MAVSDK) on Windows 11 OS. I've installed Docker Desktop on Windows. I've also added two rules for incoming and outgoing connections for the UDP port in the Windows Firewall.
I tried running the following commands, but no luck.
Logs: