e32d26cb59
This endpoint was useful when libnetwork was a standalone component that could be integrated with other products, but now that libnetwork is part of moby/moby, and considered an internal package, we're sure that the Engine's SIGUSR1 handler is available to dump stack traces. No need to keep a duplicate feature. Moreover, this endpoint is only available over an HTTP server listening on 127.0.0.1 (hardcoded), and the stackdump is always written to the disk. So, to have use of it, you need access to the host anyway. Finally, unlike the Engine's SIGUSR1 handler, this endpoint write stack traces to `/tmp` and not to the daemon's `--data-root`. This is a non-core feature, there's an alternative available, it's not documented in libnetwork/cmd/diagnostic/README.md (which is the only place that mentions the diag server AFAIK), and the diag client doesn't support it, so drop it unceremoniously. Signed-off-by: Albin Kerouanton <albinker@gmail.com>
libnetwork - networking for containers
Libnetwork provides a native Go implementation for connecting containers
The goal of libnetwork is to deliver a robust Container Network Model that provides a consistent programming interface and the required network abstractions for applications.
Design
Please refer to the design for more information.
Using libnetwork
There are many networking solutions available to suit a broad range of use-cases. libnetwork uses a driver / plugin model to support all of these solutions while abstracting the complexity of the driver implementations by exposing a simple and consistent Network Model to users.
Contributing
Want to hack on libnetwork? Docker's contributions guidelines apply.
Copyright and license
Code and documentation copyright 2015 Docker, inc. Code released under the Apache 2.0 license. Docs released under Creative commons.