Comment 1 for bug 1994488

This happens because the container provisioner is not started via dependency engine, rather by the machine agent directly.

So the normal mechanism whereby a worker would be restarted when its dependencies bounce due to an error, is not in play.