albert-a

local read: IOPS=12308, BW=48.1MiB/s write: IOPS=4111, BW=16.0MiB/s

nfs3-ganesha read: IOPS=7039, BW=27.5MiB/s write: IOPS=2352, BW=9.2MiB/s

nfs3-kernel read: IOPS=6571, BW=25.7MiB/s

Experimental Docker Libnetwork DHCP Driver

The DHCP driver is intended for users to be able to integrate Docker IP address management with their existing IPAM strategies that use DHCP for dynamic address assignment. DHCP enables users to allocate addresses in an organized fashion that will prevent overlapping IP address assignment by associating a unique MAC address from the container eth0 Ethernet interface to an IP address as determined by the DHCP pools defined in the DHCP configuration.

This driver only provides the DHCP client functionality. It does not include a DHCP server. The default driver offers single-host IPAM or for distributed multi-host orchestrated IPAM see the libnetwork overlay driver.

Getting Started

Download the driver compiled into Docker Engine - docker binary with libnetwork test dhcp client spam driver

	#!/bin/bash

	# This script is based on https://unix.stackexchange.com/revisions/480191/9.

	# Recommended SIZE setting for different drives:
	# (SATA) SSD: 1024
	# (ANY) HDD: 256
	# (High End NVME) SSD: 4096
	# (Low-Mid End NVME) SSD: 1024

	"""
	Runs a DBus message loop with a callback to receive... pretty much
	anything on a session bus.
	Listen to the Notify event; if it's a message we hate, record it, then
	listen for the return message, and kill that message.

	Tested On:
	- Ubuntu 18.04.5 LTS, CPython 3.6.9 (dbus: 1.2.6, gi: 3.26.1)

	To test, try running the following with and without this script running: