Container communication in Drive Orin

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.8.1
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
1.9.3.10904
other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

Can we have solution for this issue Container Communication in Drive Orin

Dear @arpit.agarkar,
From the old thread I can see it is expected to have perf drop when both containers use same host networking. May I know why are looking for this use case? We never heard of any customer use cases to have communication across dockers on Orin.

Use case is proving the communication between a device (Jetson Orin) and two containers running on the drive orin.

I basically have to get the data coming from Jetson Orin into both of the containers running on Drive Orin and send back the output again to Jetson Orin.

P.S : Its not necessary to establish communication between 2 containers , only data should go to both the containers without any issue

Any update on this issue ?

Dear @arpit.agarkar,
Does the use case can be reproduced using scp or iperf. It is not clear how to reproduce the issue. Also, is it happening when using x86 instead of Jetson Orin?

I am using vsome-IP protocol for communication basically

Dear @arpit.agarkar,
Could you share the repro steps and configuring vsome-IP communication?

Dear @arpit.agarkar,
Could you provide any update?

We have found out that the issue was due to vsomeip because the communication via other protocols was happening

1 Like

Thanks for update. We are closing the topic.