Re: how to wait for nested container launch in tests

> On Jun 30, 2017, at 11:23 AM, Jie Yu wrote: > > One way is to define a health check? Good idea, I'll give that a crack > > - Jie > > On Fri, Jun 30, 2017 at 3:36 AM, James Peach wrote: > >> Hi all, >> >> I'm trying to write a nested container test

Re: how to wait for nested container launch in tests

One way is to define a health check? - Jie On Fri, Jun 30, 2017 at 3:36 AM, James Peach wrote: > 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

how to wait for nested container launch in tests

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