Sign inSign up

szabis/iventoy

By szabis

•Updated about 17 hours ago

iVentoy is a complete PXE server that includes the services to enable for a PC to boot over network.

Image
Networking
18

100K+

szabis/iventoy repository overview

⁠iVentoy

A Docker image running iVentoy⁠.

iVentoy is a complete PXE boot server that includes the necessary services to enable computers to boot over network.

If you don't know what PXE, DHCP or TFTP is, don't try it!

It is recommended to use with a third-party DHCP Server iVentoy and Thirdy-part DHCP Server⁠

DirectoryMount pointDescription
data/opt/iventoy/dataFor License file, config files.
driver/opt/iventoy/driverFor driver files used by the driver mode option.
iso/opt/iventoy/isoFor ISO files.
log/opt/iventoy/logFor log files.
user/opt/iventoy/userFor user files, third-part software, auto install scritps ...

⁠What's new

  • iVentoy updated to 1.0.43 version.
  • When auto start failed, the WebUI still available instead of full quit.
  • Fix issue that unattend script does not take effect when wimboot Windows ISO.
  • Optimize boot process for Fedora/CentOS/antix/gentoo/Kylin/manjaro/pve/...
  • Bugfix.

Previous release changelog: changelog.szabis.hu⁠. For more information please visit: iVentoy GitHub⁠.

⁠First start

Important: on the first start run the container with AUTO_START_PXE=false.

The shipped default config has the internal DHCP server enabled. With auto start turned on the PXE service tries to come up with that setting and fails, so the container does not start.

  1. Start the container with AUTO_START_PXE=false.
  2. Open the WebUI at http://<host-ip>:26000 and set the DHCP mode you want to use (e.g. external DHCP server), then save the configuration.
  3. Set AUTO_START_PXE=true and recreate the container.

⁠Command line startup:

This container must be run as root.

On the first start use AUTO_START_PXE=false, see First start⁠.

docker run -d --name iventoy \
  --network host \
  --privileged \
  --restart on-failure:3 \
  --health-cmd="curl --fail --silent --head http://localhost:26000/ || exit 1" \
  --health-interval=30s \
  --health-timeout=10s \
  --health-retries=3 \
  --health-start-period=2m \
  -e AUTO_START_PXE=true \
  -e TZ=Your timezone \
  -v /path/to/data:/opt/iventoy/data \
  -v /path/to/driver:/opt/iventoy/driver \
  -v /path/to/iso:/opt/iventoy/iso \
  -v /path/to/log:/opt/iventoy/log \
  -v /path/to/user:/opt/iventoy/user \
  -p 67:67/udp \
  -p 69:69/udp \
  -p 3260:3260/tcp \
  -p 10445:10445/tcp \
  -p 10809:10809/tcp \
  -p 12049:12049/tcp \
  -p 16000:16000/tcp \
  -p 26000:26000/tcp \
  szabis/iventoy:latest

⁠Docker Compose

This container must be run as root.

On the first start use AUTO_START_PXE=false, see First start⁠.

version: '3.9'
services:
  iventoy:
    image: szabis/iventoy:latest
    network_mode: "host"
    container_name: iVentoy
    hostname: iventoy
    healthcheck:
      test: ["CMD", "curl", "--fail", "--silent", "--head", "http://localhost:26000/"]
      interval: 30s
      timeout: 10s
      retries: 3
      start_period: 2m
    privileged: true # must be true
    environment:
      - AUTO_START_PXE=true
      - TZ=Your timezone
    ports:
      - "67:67/udp" # DHCP Server
      - "69:69/udp" # TFTP Server
      - "3260:3260" # iSCSI Server
      - "10445:10445" # SMB Server (Samba)
      - "10809:10809" # NBD Server (NBD)
      - "12049:12049" # NFS Server
      - "16000:16000" # PXE Service HTTP Server (iVentoy PXE Service)
      - "26000:26000" # PXE GUI HTTP Server (iVentoy GUI)
    volumes:
      - /path/to/data:/opt/iventoy/data
      - /path/to/driver:/opt/iventoy/driver
      - /path/to/iso:/opt/iventoy/iso
      - /path/to/log:/opt/iventoy/log
      - /path/to/user:/opt/iventoy/user
    restart: on-failure:3

Tag summary

Content type

Image

Digest

sha256:6de8be84e…

Size

72.7 MB

Last updated

about 17 hours ago

docker pull szabis/iventoy