Pires

I strongly suggest to drop this in favor of supporting Mesos 1.x and the v1 API in the short term. /cc @jdef

With the release of Mesos 1.0 and v1 API becoming stable, I believe this no longer makes sense. Therefore, I strongly suggest to drop this in favor of supporting Mesos...

Refs #114

I'd also suggest moving to Quay.io, as it's much faster than Docker Hub and provides features such as container image vulnerability scan.

Done @jdef.

Force pushed due to conflicts with `master` branch.

@jdef did you address the aforementioned feedback in the latest package?

Could this be a file-description (connection?) leak?

With the release of Mesos 1.0 and v1 API becoming stable, I believe this no longer makes sense. Therefore, I strongly suggest to drop this in favor of supporting Mesos...

Care to review this, @spacejam, and update if necessary?