Isolates any given process using the unshare() system call. Suited for ROS, though can work for any process.
Since the system call is linux specific, this would not work on Windows.
This can be really useful for running a large number of tests in parallel wihtout having them interacting with each other.
This is similar to ROS domain IDs, though domain IDs are limited by the number of ports you have, and this approach is more scalable.
Originally added in drake-ros
This is a python ROS2 package, and requires colcon to be installed.
mkdir ~/my_ws
cd ~/my_ws ; mkdir src ; cd src
git clone https://github.com/adityapande-1995/linux_isolate_process
cd ~/my_ws
colcon build
source ~/my_ws/install/setup.bash
python3 -m linux_isolate_process <your command>
# For e.g., to get a bash shell that is isolated
python3 -m linux_isolate_process /bin/bash
For example, to run an isolated talker (Note : any ros nodes inside the bash -c "(<command>)" will be able to talk to each other) :
python3 -m linux_isolate_process /bin/bash -c "ros2 run demo_nodes_cpp talker"
If you open another terminal and run a listener normally, using
ros2 run demo_nodes_cpp listener
it will not receive any of the messages published by the talker. However, if you run the talker and listener in the same process, they will be able to talk to each other. That is, this should work perfectly fine :
python3 -m linux_isolate_process /bin/bash -c "ros2 run demo_nodes_cpp talker & ros2 run demo_nodes_cpp listener"
The talker and listener in this case are "isolated together", and hence can talk to each other.
Python 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import linux_isolate_process as i
>>> i.create_linux_namespaces()
True
>>> # Any ros2 nodes run here would be isolated