docker container

[ElliotHYLee]

Can a docker container access to the host machine's published topic? My naive approach doesn't seem to work. Please share if you have any suggestions. Interestingly, in the container, i can list and can see the io2x files. but it doesn't seem to receive the data.

This python works on the host but not the container.

  while not self.stop_event.is_set():
      if self.stop_event.is_set():
          break
  
      sample = subscriber.receive()
      if sample is None:
          print("nothing")  # only this comes out in the container
          continue

Everything same version 0.7.0, python3.12.

inside-docker terminal

cd /dev/shm/
ls
iox2_~~~
iox2_~~~

and

(base) root@xxxxx:/home/ubuntu# ls -l /tmp/iceoryx2/services
total 12
-r-------- 1 ubuntu ubuntu 783 Dec  4 17:07 iox2_1cc8a550755e2216143ee2c8ae860404cb639739.service
-r-------- 1 ubuntu ubuntu 784 Dec  4 17:07 iox2_6ad1debfd74cc2b0e59ced5bf37eb0f70233b197.service
-r-------- 1 ubuntu ubuntu 783 Dec  4 17:07 iox2_c47675e555d06ae0e603e6cd82f51ed5168cee22.service
(base) root@xxxxxx:/home/ubuntu# ls -l /dev/shm | grep iox2_
-rwx------ 1 ubuntu ubuntu 125340070 Dec  4 17:07 iox2_0354a209029e7d094a819e2d4030ea331e6caaf0_171152071771449022916054759119.data
-rwx------ 1 ubuntu ubuntu 125340070 Dec  4 17:07 iox2_0354a209029e7d094a819e2d4030ea331e6caaf0_250505533093857757837987428047.data
-rwx------ 1 ubuntu ubuntu 125340070 Dec  4 17:48 iox2_0354a209029e7d094a819e2d4030ea331e6caaf0_91501862233472308643534747343.data
-rwx------ 1 ubuntu ubuntu      1443 Dec  4 17:07 iox2_305ad9523c6b202364d581359ec3d2c5743e42e7_1cc8a550755e2216143ee2c8ae860404cb639739.dynamic
-rwx------ 1 ubuntu ubuntu      1443 Dec  4 17:07 iox2_305ad9523c6b202364d581359ec3d2c5743e42e7_6ad1debfd74cc2b0e59ced5bf37eb0f70233b197.dynamic
-rwx------ 1 ubuntu ubuntu      1443 Dec  4 17:07 iox2_305ad9523c6b202364d581359ec3d2c5743e42e7_c47675e555d06ae0e603e6cd82f51ed5168cee22.dynamic

docker-compose.yml

  ...
  ipc: host
  volumes:
    - /dev:/dev
    - /tmp:/tmp
  environment:
    - DISPLAY

[elBoberido]

@ElliotHYLee if the users in the docker do not match the users on your host, the communication cannot be established, due to the zero-trust approach of iceoryx2. But there is the dev_permissions feature flag to enable processes of all users to communicate with each other. This is a workaround for a docker container which users are not set up the same way as on the host system. It is not meant to be used in production, though.

[ElliotHYLee]

Ah, the user ids in both host and container just needs to be the same! Thanks it works!

I just created a new user id in the container same as host.