Pumba fails when container is killed while running netem delay

[dipe3418]

@alexei-led If one of the containers are killed while running the netem delay cmd, Pumba is throwing a fatal error message.

• Running netem delay cmd using Pumba docker container:
  docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock gaiaadm/pumba --log-level=info netem --tc-image "gaiadocker/iproute2" --duration 60s delay --time 500 "re2:^test"

• Kill container to simulate a failing health check in AWS ECS for example:
  docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock gaiaadm/pumba --random --log-level=info kill --signal=SIGKILL "re2:^test" INFO[0000] killing container dryrun=false id=28b884fc6bda47fab1dd771319a25642936865243cf4e84ae49c10324959543e name=/test_10 signal=SIGKILL

• Pumba docker container stops with Fatal error msg
  WARN[0064] failed to delay network for container error="failed to stop netem: failed to start tc-container: Error response from daemon: No such container: 28b884fc6bda47fab1dd771319a25642936865243cf4e84ae49c10324959543e" FATA[0064] failed to delay packets for one or more containers: failed to stop netem: failed to start tc-container: Error response from daemon: No such container: 28b884fc6bda47fab1dd771319a25642936865243cf4e84ae49c10324959543e

Is there a way to keep Pumba running when one of the containers is killed?