Workaround odd Start() behavior
Workaround odd Start() behavior

During a recent scale test I've noticed quite a number of containers
(around 1%) supposdely failing to start according to forkstart logging,
but without any actual error being reported in lxc.conf or lxc.log and
the container running very happily.

My best guess is that "something" is wrong in liblxc when under very
heavy load and causes go-lxc to return an error value rather than
success.

So let's just check whether the container did succeed to start and if it
did, skip the error.

Signed-off-by: Stéphane Graber <089afc6d81f66f1168a9849e15660feae286e024@ubuntu.com>

pcdummy/lxd,lxc/lxd,lxc/lxd,jsavikko/lxd,pcdummy/lxd,akshaykarle/lxd,atxwebs/lxd,lxc/lxd,stgraber/lxd,atxwebs/lxd,Skarlso/lxd,chrisglass/lxd,lxc/lxd,hallyn/lxd,stgraber/lxd,Skarlso/lxd,erikmack/lxd,Skarlso/lxd,hallyn/lxd,jsavikko/lxd,ollie314/lxd,ollie314/lxd,hallyn/lxd,mjeanson/lxd,georghopp/lxd,jsavikko/lxd,hallyn/lxd,lxc/lxd,techtonik/lxd,akshaykarle/lxd,atxwebs/lxd,akshaykarle/lxd,stgraber/lxd,georghopp/lxd,stgraber/lxd,atxwebs/lxd,lxc/lxd,techtonik/lxd,stgraber/lxd,mjeanson/lxd,stgraber/lxd,hallyn/lxd,georghopp/lxd,chrisglass/lxd,pcdummy/lxd,chrisglass/lxd,erikmack/lxd,Skarlso/lxd,lxc/lxd,ollie314/lxd,techtonik/lxd,stgraber/lxd,erikmack/lxd,mjeanson/lxd,hallyn/lxd