Hi all, I'm trying to write a nested container test for an isolator. It turns out that the default executor sends TASK_RUNNING immediately after receiving the LAUNCH_NESTED_CONTAINER response. However, at this time the nested container is not actually up, and the command specified in the task info hasn't been launched. Can anyone suggest a way for a test to detect that the nested container command is actually running, so that I can advance the clock to reliably trigger the isolator?
J
