Network drive creation?

user10e32 · November 21, 2017, 6:56pm

1.) Is it possible to create my own network drive from scratch that does not extend bridge network?
2.) Where can I found any tutorials about that (I have no idea how to search about it)?
3.) Where can I found the default network drives codes (bridge, none, host)?
4.) How to add new drives, that does not extend bridge network (that I have created based on such code)?

I have read about network driver plugins but have not understand it completly:
1.) How can I create network drive plugins?
2.) If I have create network drive plugin then is its properties similar to default network drive - general usage (can I create that way my own network drive)?

sdetweil · November 21, 2017, 8:45pm

see

github.com

docker/libnetwork/blob/master/docs/remote.md

Remote Drivers
==============

The `drivers.remote` package provides the integration point for dynamically-registered drivers. Unlike the other driver packages, it does not provide a single implementation of a driver; rather, it provides a proxy for remote driver processes, which are registered and communicate with LibNetwork via the Docker plugin package.

For the semantics of driver methods, which correspond to the protocol below, please see the [overall design](design.md).

## LibNetwork integration with the Docker `plugins` package

When LibNetwork initialises the `drivers.remote` package with the `Init()` function, it passes a `DriverCallback` as a parameter, which implements `RegisterDriver()`. The remote driver package uses this interface to register remote drivers with LibNetwork's `NetworkController`, by supplying it in a `plugins.Handle` callback.

The callback is invoked when a driver is loaded with the `plugins.Get` API call. How that comes about is out of scope here (but it might be, for instance, when that driver is mentioned by the user).

This design ensures that the details of driver registration mechanism are owned by the remote driver package, and it doesn't expose any of the driver layer to the North of LibNetwork.

## Implementation

The remote driver implementation uses a `plugins.Client` to communicate with the remote driver process. The `driverapi.Driver` methods are implemented as RPCs over the plugin client.

The payloads of these RPCs are mostly direct translations into JSON of the arguments given to the method. There are some exceptions to account for the use of the interfaces `InterfaceInfo` and `JoinInfo`, and data types that do not serialise to JSON well (e.g., `net.IPNet`). The protocol is detailed below under "Protocol".

This file has been truncated. show original

Topic		Replies	Views
New to Docker need assistance General	6	2462	March 3, 2018
A little network fundamentals share General docker	0	571	February 28, 2018
Docker networking without IP addresses (for SDN) General	7	6814	September 25, 2017
Best Practice? Configuring docker service and containers with a custom Linux Bridge Device General	1	1901	August 26, 2014
Is it possible to change default network drive from bridge to nat? General	0	981	October 15, 2021

Network drive creation?

Related topics