mirrors/docker-netbootxyz
1
0
Fork 0
mirror of https://github.com/netbootxyz/docker-netbootxyz.git synced 2025-08-08 07:07:29 +02:00
Code Issues Packages Projects Releases Wiki Activity

proxydhcp: capabilities and network mode

Browse Source
This commit is contained in:
Robert Coleman 2025-01-15 10:55:20 +13:00
parent cfc13acd26
commit 43b5988f30
No known key found for this signature in database
2 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -66,6 +66,8 @@ docker run -d \
-p 8080:80 `# optional, destination should match ${NGINX_PORT} variable above.` \ -p 8080:80 `# optional, destination should match ${NGINX_PORT} variable above.` \
-v /local/path/to/config:/config `# optional` \ -v /local/path/to/config:/config `# optional` \
-v /local/path/to/assets:/assets `# optional` \ -v /local/path/to/assets:/assets `# optional` \
--cap-add NET_ADMIN `# only required for DHCP Proxy mode` \
--network host `# only required for DHCP Proxy mode` \
--restart unless-stopped \ --restart unless-stopped \
ghcr.io/netbootxyz/netbootxyz ghcr.io/netbootxyz/netbootxyz
``` ```
@ -127,7 +129,7 @@ Container images are configured using parameters passed at runtime (such as thos
This image requires the usage of a DHCP server in order to function properly, unless you enable the **optional proxy-DHCP mode**. If you have an existing DHCP server, you will need to make some small adjustments to forward requests to the netboot.xyz container. You will typically set your `next-server` and `boot-file-name` parameters in the DHCP configuration. This tells DHCP to forward requests to the TFTP server and then select a boot file from the TFTP server. This image requires the usage of a DHCP server in order to function properly, unless you enable the **optional proxy-DHCP mode**. If you have an existing DHCP server, you will need to make some small adjustments to forward requests to the netboot.xyz container. You will typically set your `next-server` and `boot-file-name` parameters in the DHCP configuration. This tells DHCP to forward requests to the TFTP server and then select a boot file from the TFTP server.
If you prefer not to modify your existing DHCP server, you can enable the **proxy-DHCP mode** by setting the `DHCP_RANGE_START` environment variable to the first IP in your DHCP range (e.g. 192.168.1.1). This mode allows netboot.xyz to provide PXE boot configuration while your existing DHCP server continues to handle IP address assignment. If you prefer not to modify your existing DHCP server, you can enable the **proxy-DHCP mode** by setting the `DHCP_RANGE_START` environment variable to the first IP in your DHCP range (e.g. 192.168.1.1). This mode allows netboot.xyz to provide PXE boot configuration while your existing DHCP server continues to handle IP address assignment. This mode requires the docker (or docker compose) parameter `--cap-add NET_ADMIN` be added and for the container to be running directly on the network to see the DHCP messages, i.e. with network mode set to `host` or via `ipvlan`/`macvlan` or a bridge.
### Examples ### Examples

3
docker-compose.yml.example
View File

@ -17,3 +17,6 @@ services:
- 69:69/udp - 69:69/udp
- 8080:80 # optional, destination should match ${NGINX_PORT} variable above. - 8080:80 # optional, destination should match ${NGINX_PORT} variable above.
restart: unless-stopped restart: unless-stopped
# cap_add:
# - NET_ADMIN # required for DHCP Proxy mode.
# network_mode: host # required for DHCP Proxy mode - network mode host, (or ipvlan/macvlan or a bridge).