Iceoryx2 in Kubernetes, FailedToDeliverSignal. #1107
Replies: 1 comment 13 replies
-
@DrissiReda we did not yet try to run iceoryx2 within a Kubernets pod. In theory this should work. Only inter-pod communication is a bit challenging. From my limited understanding of Kubernets, it should be possible to have a shared memory communication between container in the same pod. Are you able to run the basic pub-sub example in multiple container? This will give us more information. By default, iceoryx2 uses If the events with the unix domain sockets do not work, there is also an alternative implementation with semaphores which are placed in shared memory. So if the basic pub-sub example works, it would be worth a try to check if the semaphore based event implementation works across container boundaries. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, did anyone ever use iceoryx2 in Kubernetes?
I want to run a pod with multiple containers that communicate with each other via iceoryx2. I used the event based communication rust example.
With docker compose it works well simply by mounting the same
/dev/shm
to all services.I thought it would be the same with Kubernetes, simply creating an emptyDir and mounting it to
/dev/shm
and addingshareProcessNamespace: true
but that is clearly not enough.I don't think the issue is with the code because it still works well and communication indeed does take place, I just keep getting this warning.
I'm getting this warning by the sender when it is supposed to notify the next container.
Does anybody have any idea?
Here is the warning:
Beta Was this translation helpful? Give feedback.
All reactions