Docker and WhatPulse

The developer product Docker and the WhatPulse do currently not play well together. 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. The current workaround is to disable network measurements in the client and restarting it before working with Docker.

A fix is pending.