Skip to content

Conversation

@nathanhammond
Copy link
Owner

This PR removes the check for existence of a network driver prior to attempting use.

Plugins are not activated automatically at Docker daemon startup. Rather, they are activated only lazily, or on-demand, when they are needed. https://docs.docker.com/engine/extend/plugin_api/#plugin-activation

As a consequence, if you write a custom network driver and attempt to use it for your Azure Pipelines Agent, the plugin has not been registered at that time.

You instead get the warning message and shunted back to the default.

This code was added in microsoft#3751 and this would be the first update since landing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants