Skip to content

Latest commit

 

History

History
46 lines (34 loc) · 1.14 KB

dhcp.md

File metadata and controls

46 lines (34 loc) · 1.14 KB
Raw
title description date toc draft weight
dhcp plugin
plugins/ipam/dhcp/README.md
2017-08-11
true
false
200

Overview

With dhcp plugin the containers can get an IP allocated by a DHCP server already running on your network. This can be especially useful with plugin types such as macvlan. Because a DHCP lease must be periodically renewed for the duration of container lifetime, a separate daemon is required to be running. The same plugin binary can also be run in the daemon mode.

Operation

To use the dhcp IPAM plugin, first launch the dhcp daemon:

# Make sure the unix socket has been removed
$ rm -f /run/cni/dhcp.sock
$ ./dhcp daemon

If given -pidfile <path> arguments after 'daemon', the dhcp plugin will write its PID to the given file.

Alternatively, you can use systemd socket activation protocol. Be sure that the .socket file uses /run/cni/dhcp.sock as the socket path.

With the daemon running, containers using the dhcp plugin can be launched.

Example configuration

{
	"ipam": {
		"type": "dhcp",
	}
}

## Network configuration reference

* `type` (string, required): "dhcp"