A Docker image serving as a standalone PXE (running Dnsmasq). This server can be placed in an existing network infrastructure with an already configured DHCP server or in a network without any DHCP server.
This PXE currently serves:
These are the dependencies required to build and run the box:
- Docker 1.12+
How to run
ENTRYPOINT of this image is set to run
no-daemon mode. Add your desired
dhcp-ranges as command line options (see dnsmasq documentation for details). Note that you can specify more than one range by adding multiple
The easiest way to use instances of this image to provide a PXE in an existing network is to run a container based on it with the
To sum up:
docker run -it --rm --net=host ferrarimarco/pxe
If you want to inspect the container just run it overwriting the entrypoint:
Integrated DHCP server
If you want to enable the integrated DHCP server for a given IP address range add a
x.x.x.x is the start of the range,
y.y.y.y is the end and
z.z.z.z is the subnet mask.
Standalone DHCP server
If you want to use an existing DHCP server and let
dnsmasq handle only the PXE, add a
x.x.x.x is the IP address of the server running dnsmasq.
How to modify the configuration
All the configuration files can be modified at will. Just look at the Dockerfile to see where they are (mainly in
/var/lib/tftpboot) and overwrite them with your own (mounting volumes from the Docker host or rebuilding the image).
Additional PXE Boot Menu Entries
If you just want to add additional menu entries to the boot menu, just overwrite the contents of
The syntax for this file is described in the syslinux documentation.
Example: 2nd Memtest86+ plus Ubuntu 16.04 Boot Options
Here is an
additional_menu_entries file to include (along with the default Memtest86+) two additional boot options: a customized Memtest86+ and Ubuntu 16.04.
LABEL memtest86-2 MENU LABEL Memtest86+ 2nd entry KERNEL /memtest/memtest86+ LABEL ubuntu-16-04-amd64 MENU LABEL Ubuntu 16.04 amd64 KERNEL /ubuntu/16.04/16.04.2-server-amd64/install/netboot/ubuntu-installer/amd64/linux APPEND /install/vmlinuz auto=true interface=eth0 hostname=cluster domain=home url=tftp://192.168.56.2/preseed/16.04/preseed.cfg initrd=ubuntu/16.04/16.04.2-server-amd64/install/netboot/ubuntu-installer/amd64/initrd.gz debian-installer=en_US locale=en_US kbd-chooser/method=us keyboard-configuration/modelcode=SKIP keyboard-configuration/layout=USA keyboard-configuration/variant=USA console-setup/ask_detect=false --
Testing and validating the setup
- Virtualbox 5.1.16+
- Vagrant 1.9.3+
How to run
After running the container with a suitable DHCP configuration (see above for instructions) and the
--net=host option, you can run
vagrant up from the root of the project. A Virtualbox VM (with a NATed network adapter) will boot from the given PXE.
Note that you should check the IP address ranged configured by the Virtualbox DHCP server (if enabled) and configure your
If Virtualbox DHCP server assigns addresses in the
192.168.56.0/24 subnet, then the
dhcp-range could be:
192.168.56.2 is the address assigned to the PXE server. Remember to also update the IP addresses in
/var/lib/tftpboot/pxelinux.cfg/default if you serve any content from the TFTP server (like a
preseed.cfg for example) to point to the IP address of the container running this PXE. For this reason it could be useful to manually assign (or reserve) ip addresses for containers running this PXE.
If you have suggestions, please create a new GitHub issue or a pull request.