#Libnetwork plugin for Calico

This plugin for Docker networking (libnetwork) is intended for use with Project Calico. Calico can be deployed on Docker using guides from the calico-docker repository.

##How to Run It When deployed using calicoctl (see calico-docker) simply pass in the --libnetwork flag.

• To run a specific version of the plugin use the --libnetwork-image flag.

Prebuilt docker images are available on DockerHub with tags available for each libnetwork-plugin release.

The container needs to be run using docker run -d --privileged --net=host -v /run/docker/plugins:/run/docker/plugins calico/node-libnetwork

• Privileged is required since the container creates network devices.
• Host network is used since the network changes need to occur in the host namespace
• The /run/docker/plugins volume is used to allow the plugin to communicate with Docker.

If you don't have etcd available at localhost:4001 then you need to pass in the location as an environment variable e.g. -e ETCD_AUTHORITY=1.2.3.4:2379

To run the plugin from source use gunicorn e.g. sudo gunicorn -b unix:///run/docker/plugins/calico.sock libnetwork.driver_plugin:app

For the full list of recommended options for use in production, see start.sh

For testing out changes, add the --reload flag or use make run-plugin-local

Install the dependencies from requirements.txt using pip install -r requirements.txt

Logs are sent to STDOUT. If using Docker these can be viewed with the docker logs command.

This currently requires a rebuild. Change the line towards the top of the plugin code

These don't include interactions from the Docker daemon or felix. These are interactions from the libnetwork-plugin only

See the main Calico documentation

Further sources of getting help are listed in the calico-docker repository.