So I'm having a strange problem with running ROS inside a [Singularity](http://singularity.lbl.gov/) container. First, I'm using Singularity because that is what is supported by the cluster at my university (version 2.3 if that is of any help), second I'm building my container from a Docker image as supported by Singularity.
The image is using ROS Kinetic with Gazebo 8 (the problem also occurs with Gazebo 7). The problem occurs right after start. Both Gazebo and my node is started and everything waits for the robot to spawn inside Gazebo. Once this is verified my experiments begin. From the output I can see that my code is started, waiting and then starts the experiment and is able to complete one round of evaluation before the whole setup crashes. From the `master.log` I can see only one error which is a `exception=[Errno 111] Connection refused` coming from a `publisherUpdate[/clock]`. This does not happen right away and from looking at the log in `rosout.log` it seems that the problem does not occur until after one evaluation. The problem does not occur when running the code on my local machine which leads me to believe that the problem is caused by interactions between ROS/Singularity and possibly the cluster setup. The strange thing is that the problem does not happen right away. If that was the case I would be sure that it was Singularity, but since my code runs and the time (from `rosout.log`) is reset once it seems that `/clock` is successfully published before the problem occurs.
I'm hoping that someone has some pointers on where I can start to debug this problem as I do not know where to go from here. I'll attach the full logs [`master.log`](http://ix.io/y5W), [`rosout.log`](http://ix.io/y5X)
↧