← Directory

EasyPXE-DNSMasq

EasyPXE DNSMasq provides proxyDHCP and TFTP services for the EasyPXE network boot stack.

  • Network Services
  • Tools & Utilities
EasyPXE DNSMasq provides proxyDHCP and TFTP services for the EasyPXE network boot stack. It works alongside your existing router DHCP server and supplies PXE boot information to Legacy BIOS and UEFI clients. This container requires host networking because it must receive DHCP broadcasts and provide TFTP and proxyDHCP services.

Platform availability

Available on 1 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

39/100 Low

Maintained
66last commit 120 days ago
Popular
102 GitHub stars
Easy to install
201 install platform, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 13 days ago

GitHub stars
2
Open issues
0
Last commit
2026-06-15
Activity
stale

Checked 5 days ago - source: GitHub (OKiU-Network-Europe/EasyPXE-Unraid)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 14 days ago - source: Docker Hub image tags and published docs

First-install notes

No first-install notes yet.

Alternatives

No alternatives collected yet.

Common questions

Does EasyPXE-DNSMasq replace my router’s DHCP server?

No, it runs dnsmasq in proxyDHCP mode so clients still get their IP address from the existing router. It only adds PXE boot information, and no router changes are needed.

Which ports are used by the EasyPXE stack?

TFTP runs on UDP 69 for the bootloader, and the HTTP menu runs on port 8080 by default. Set HTTP_PORT in the .env file if you need a different HTTP port because Unraid uses port 80 for its UI.

Where should I put ISO files for the boot menu?

Put them in /mnt/user/isos by default, because docker-compose bind-mounts that share as /isos on the HTTP server. If your ISO share is in another path, edit the volume line in docker-compose.yml.

Can I change boot menus without restarting the container?

Yes, edit http/menus/local.ipxe and the changes take effect immediately. The stack fetches the menu fresh on every boot, so no container restart is needed for menu changes.

How can I confirm the PXE services are responding?

From another LAN machine, retrieve undionly.kpxe with TFTP and request the boot.ipxe file from the HTTP server. You can also watch the dnsmasq container logs with docker logs -f pxe-dnsmasq.

Answers sourced from github.com

Community

Collected 9 days ago - public community threads