- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
From the issue, I understand that ROS2 communication from the docker container is being established to the ROS2 on local Jetson which is hosted locally. However from local machine connecting to ROS2 on docker container hosted on AWS, the connection is failing.
The following things can be verified which can help for this issue:
- Connectivity to the AWS Machine which is having docker container running from local Jetson machine.
- We need to check if the machine is backed in a private subnet or public subnet. If is it backed by private subnet, please try changing the machine to a public subnet and verify the setup.
- Please verify if the docker container is exposed on any port number of host machine. Please refer the document [1] to expose the container on a port number.
I request to please verify the above steps which might help in resolving your issue.
References:
[1] https://docs.docker.com/engine/reference/commandline/run/#publish
Thank you for your answer.
1- The connection to AWS is well established: i can ping the public IP address of the AWS EC2 instance from a terminal in Jetson. But it is worth noting that i don't know how to ping the local Jetson from the container running on AWS.
2- Here is the output for <ifconfig> in my AWS EC2 docker container:
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
inet6 fe80::42:86ff:fe61:d021 prefixlen 64 scopeid 0x20<link>
ether 02:42:86:61:d0:21 txqueuelen 0 (Ethernet)
RX packets 54927 bytes 3403097 (3.4 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 58546 bytes 831783306 (831.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ens5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9001
inet 172.31.29.173 netmask 255.255.240.0 broadcast 172.31.31.255
inet6 fe80::8:77ff:fed6:4bea prefixlen 64 scopeid 0x20<link>
ether 02:08:77:d6:4b:ea txqueuelen 1000 (Ethernet)
RX packets 2283142 bytes 2372429596 (2.3 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1255472 bytes 330288429 (330.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 657439 bytes 1488374869 (1.4 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 657439 bytes 1488374869 (1.4 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
3- I already created the docker container with argumet: --network=host to expose all the container ports (I also tried --network=bridge)
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 10 Monaten