Self-host netboot.xyz with Levelrail
Network boot menu for installers and rescue tools, served by the official container with its web configuration page and asset mirror.
- Authornetbootxyz
- LicenceApache-2.0
- Memory256 MiB
- Services1
How to self-host netboot.xyz
-
Pull the images
One image is pulled on your server.
Show images
netbootxyz/netbootxyz:0.7.6-nbxyz27
-
Create the app
One service starts in a single Compose app, with 2 named volume mounts for your data, on ports 3000, 8080.
-
Fill in the secrets
You do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
After the first start
- Open the address to manage menus and download boot assets. Boot clients still need DHCP options pointing at this host's TFTP port.
netboot.xyz requirements
- Memory
- About 256 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 3000, 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- Apache-2.0, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then netboot.xyz. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the netboot.xyz docs page.
Deploy netboot.xyz your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy netboot.xyz from the CLI
levelrail-cli templates deploy netbootxyz --name my-netbootxyz Deploy netboot.xyz with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/netbootxyz/deploy netboot.xyz configuration
netboot.xyz services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| netbootxyz | netbootxyz/netbootxyz:0.7.6-nbxyz27 | 3000, 8080 | config -> /configassets -> /assets |
netboot.xyz environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 3000, 8080
- Volumes
- 2 named mounts: config -> /config, assets -> /assets
netboot.xyz FAQ
How much memory does netboot.xyz need?
The catalog lists about 256 MiB of memory for netboot.xyz.
Does netboot.xyz run on arm64?
For netboot.xyz, arm64 support is not confirmed; amd64 is unknown.
What licence is netboot.xyz under?
netboot.xyz is licensed under Apache-2.0, which is permissive, with few conditions on reuse.
Does netboot.xyz need configuration before it starts?
No. The template fills in its own defaults.
Which ports does netboot.xyz use?
netboot.xyz listens on ports 3000 and 8080 inside the stack.
Where does netboot.xyz keep its data?
In named volumes: config mounted at /config and assets mounted at /assets.
Can I deploy netboot.xyz on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for netboot.xyz, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image netbootxyz/netbootxyz:0.7.6-nbxyz27 is what you deploy there.