Conversation
This commit also brings in the ability to specify a default network and its corresponding driver as daemon flags. This helps in existing clients to make use of newer networking features provided by libnetwork. Signed-off-by: Madhu Venugopal <[email protected]>
Signed-off-by: Madhu Venugopal <[email protected]>
|
Review this this morning with Madhu. I think the integration points for both CLI commands and API endpoints and clean and simple (directly goes to libnetwork, and it's still experimental). The one tricky thing is the dance around So LGTM for me. |
|
LGTM. Moving to docs review. |
|
I don't have scope today for a full doc review. This is in experimental I see. So, let's merge it. Just to remind everyone, experimental "docs" live in the repo and doesn't go out to docs.docker.com |
|
#boom |
There was a problem hiding this comment.
@mavenugo can you open an issue and create a follow-up PR to fill in the right link to that issue? Thanks!
7 participants
Based on various discussions and inputs, we have a simplified proposal to address the network UI
separate from services ui. This PR brings in the network ui & api provided by libnetwork and hooking it
to be part of docker.
All of these are defined under experimental tag in order to get user feedback before making it officialy into the docker ui chain.