Docker and WhatPulse

The developer product Docker and the WhatPulse do currently not play well together. Previously, reports has said that the WhatPulse client starts running at 100% CPU and starts to consume a lot of memory when a Docker instance is launched. This has been fixed in WhatPulse 2.8 by simply ignoring the Docker network interface, so traffic between containers and the host is not measured, only traffic going outside the host.