This workaround is not needed since the release of Docker 1.11.0 which addresses the underlying issue.