-
-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to chain custom.ipxe using just boot.cfg and custom.ipxe #13
Comments
Just ran into this myself. On the You can set that location to whatever you want. just keep in mind that this is NOT the same as going to the web interface and creating a new ipxe file that you name A simple cheat for all this is to set the |
@ikkemaniac I would like to use this tool in a local environment (without permanent available network access) where building images or direct filesystem access is not possible. |
No freaking clue. Note that i'm not affiliated with this project. I'd just build a custom ipxe to your liking on your favorite machine and copy that to your environment. Or use the custom_url. |
|
I want to minimize the amount of modified iPXE files so I only created
custom.ipxe
and modifiedboot.cfg
. However I cannot seem to get the menu itemcustom-user
inmenu.ipxe
. It looks like it is has two issues:1. Misconfigured setting for the Docker version which does not generate custom-user menu item
netbootxyz/netboot.xyz/blob/development/roles/netbootxyz/defaults/main.yml
custom_generate_menus: false
and this results in not creating a line in
netbootxyz/netboot.xyz/blob/development/roles/netbootxyz/templates/menu/menu.ipxe
with the resulting
menu.ipxe
filecustom.ipxe
in the web environment, shouldn't line 137 innetbootxyz/netboot.xyz/blob/development/roles/netbootxyz/templates/menu/menu.ipxe.j2
be changed from
to
The text was updated successfully, but these errors were encountered: