[GH-ISSUE #24 ] local assets aren&#39;t used - correct / default path missing from README #127

Owner

Originally created by @danboid on GitHub (Jun 13, 2022).
Original GitHub issue: https://github.com/netbootxyz/docker-netbootxyz/issues/24

I have set up a local instance of netboot.xyz 2.0.59 under Ubuntu 22.04.

I have used its web interface to download all of the assets for a couple of distros. They seemed to download fine but netboot doesn't utilise them, it still downloads them from the internet every time.

I presume this is because I haven't configured the assets path correctly when I was setting up the container. What is the correct default assets path to use when setting up the container? We should add this path to the netboot.xyz docker container docs.

Originally created by @danboid on GitHub (Jun 13, 2022). Original GitHub issue: https://github.com/netbootxyz/docker-netbootxyz/issues/24 I have set up a local instance of netboot.xyz 2.0.59 under Ubuntu 22.04. I have used its web interface to download all of the assets for a couple of distros. They seemed to download fine but netboot doesn't utilise them, it still downloads them from the internet every time. I presume this is because I haven't configured the assets path correctly when I was setting up the container. What is the correct default assets path to use when setting up the container? We should add this path to the netboot.xyz docker container docs.

kerem commented

Author

Owner

@danboid commented on GitHub (Jun 13, 2022):

I looks like the default asset path should be set to /assets/asset-mirror/releases/download or maybe it should be just /assets?

@danboid commented on GitHub (Jun 13, 2022): I looks like the default asset path should be set to `/assets/asset-mirror/releases/download` or maybe it should be just `/assets`?

kerem commented

Author

Owner

@danboid commented on GitHub (Jun 14, 2022):

I don't know how local assets are supposed to work. When I originally set up the container, I used this command:

docker run -d --name=netbootxyz -p 3000:3000 -p 69:69/udp -p 8080:80 -v /etc/netbootxyz/config:/config -v /etc/netbootxyz/assets:/assets --restart unless-stopped ghcr.io/netbootxyz/netbootxyz

I used that because I was wanting to mount a local dir ( /etc/netbootxyz/assets) in my container. It didn't seem to do that but the netboot webapp is accessible after running it. If I don't pass any -v options, I cannot access the containers web app but supposedly the -v arguments for setting asset and config dir mappings are optional?

@danboid commented on GitHub (Jun 14, 2022): I don't know how local assets are supposed to work. When I originally set up the container, I used this command: ``` docker run -d --name=netbootxyz -p 3000:3000 -p 69:69/udp -p 8080:80 -v /etc/netbootxyz/config:/config -v /etc/netbootxyz/assets:/assets --restart unless-stopped ghcr.io/netbootxyz/netbootxyz ``` I used that because I was wanting to mount a local dir ( /etc/netbootxyz/assets) in my container. It didn't seem to do that but the netboot webapp is accessible after running it. If I don't pass any `-v` options, I cannot access the containers web app but supposedly the `-v` arguments for setting asset and config dir mappings are optional?

kerem commented

Author

Owner

@danboid commented on GitHub (Jun 14, 2022):

Here's how my netboot web app asset management page looks:

I'm a bit confused by the layout of the right column. At the top it says 'Untracked assets' then immediately below that it lists the assets I downloaded. I would've expected that if I could see the assets in that list then my netboot server would use those instead of downloading them right? That's not happening but are these actually still 'untracked assets' or not? The untracked assets column heading is confusing because it looks like it is an empty list followed by another separate list of tracked assets but squashed into the same column. Is that what is being displayed here?

If those local assets are downloaded but untracked, how do I make them tracked? Conversely, it it possible to make tracked assets untracked? I'm not even sure what tracked means in this case? Is it just a synonym for 'downloaded and locally hosted'?

@danboid commented on GitHub (Jun 14, 2022): Here's how my netboot web app asset management page looks: ![netboot-assets](https://user-images.githubusercontent.com/1429783/173522878-69cb942e-a2e8-46f2-ad90-aa973639ac42.png) I'm a bit confused by the layout of the right column. At the top it says 'Untracked assets' then immediately below that it lists the assets I downloaded. I would've expected that if I could see the assets in that list then my netboot server would use those instead of downloading them right? That's not happening but are these actually still 'untracked assets' or not? The untracked assets column heading is confusing because it looks like it is an empty list followed by another separate list of tracked assets but squashed into the same column. Is that what is being displayed here? If those local assets are downloaded but untracked, how do I make them tracked? Conversely, it it possible to make tracked assets untracked? I'm not even sure what tracked means in this case? Is it just a synonym for 'downloaded and locally hosted'?

kerem commented

Author

Owner

@danboid commented on GitHub (Oct 20, 2022):

Have you had time to look at fixing this yet @antonym ?

@danboid commented on GitHub (Oct 20, 2022): Have you had time to look at fixing this yet @antonym ?

kerem commented

https://netboot.xyz/docs/docker#local-mirror-access

Author

Owner

@DarkAxi0m commented on GitHub (Nov 18, 2023):

I know this is old, but by chance if found the key point to getting local assets working.

On dashboard, edit boot.cfg, and set live_endpoint to your docker server address. Then netboot will look there for files.

@DarkAxi0m commented on GitHub (Nov 18, 2023): I know this is old, but by chance if found the key point to getting local assets working. On dashboard, edit boot.cfg, and set live_endpoint to your docker server address. Then netboot will look there for files. https://netboot.xyz/docs/docker#local-mirror-access

kerem commented

Author

Owner

@styxadmin commented on GitHub (May 24, 2024):

I know this is old, but by chance if found the key point to getting local assets working.

On dashboard, edit boot.cfg, and set live_endpoint to your docker server address. Then netboot will look there for files.

https://netboot.xyz/docs/docker#local-mirror-access

@styxadmin commented on GitHub (May 24, 2024): > I know this is old, but by chance if found the key point to getting local assets working. > > On dashboard, edit boot.cfg, and set live_endpoint to your docker server address. Then netboot will look there for files. > > https://netboot.xyz/docs/docker#local-mirror-access ![image](https://github.com/netbootxyz/docker-netbootxyz/assets/50232595/da832a57-431d-4212-b7aa-4d5d9b802b2a) ![image](https://github.com/netbootxyz/docker-netbootxyz/assets/50232595/55967d65-0721-43a9-b8ef-ef045014dd8a)

kerem commented

Author

Owner

@danboid commented on GitHub (May 28, 2024):

Thanks @DarkAxi0m! I've not tried this yet but will have to give it a go soon.

It would seem that the netboot maintainer had forgot how this was supposed to work. This should be added to the netboot docs.

@danboid commented on GitHub (May 28, 2024): Thanks @DarkAxi0m! I've not tried this yet but will have to give it a go soon. It would seem that the netboot maintainer had forgot how this was supposed to work. This should be added to the netboot docs.

kerem commented

Author

Owner

@nrvale0 commented on GitHub (Aug 19, 2024):

I've made the adjustment and I'm still not seeing PXE clients request from local live_endpoint. I'm running netboot.xyz from Docker Compose and I'm wondering if perhaps its not picking up the new setting?

@nrvale0 commented on GitHub (Aug 19, 2024): I've made the adjustment and I'm still not seeing PXE clients request from local live_endpoint. I'm running netboot.xyz from Docker Compose and I'm wondering if perhaps its not picking up the new setting?

kerem commented

Author

Owner

@danboid commented on GitHub (Aug 19, 2024):

I've not tried this myself yet but did you reboot the netboot.xyz server after changing the config? Maybe you just need to restart one of its services after changing the config?

@danboid commented on GitHub (Aug 19, 2024): I've not tried this myself yet but did you reboot the netboot.xyz server after changing the config? Maybe you just need to restart one of its services after changing the config?

kerem commented

Author

Owner

@nrvale0 commented on GitHub (Aug 19, 2024):

I've not tried this myself yet but did you reboot the netboot.xyz server after changing the config? Maybe you just need to restart one of its services after changing the config?

I've tried to restart the Compose stack including rm -rf'ing the contents of the config directory and same result. I'll loop back on it after I find a work-around for the outstanding issues with IPv6 in iPXE.

@nrvale0 commented on GitHub (Aug 19, 2024): > I've not tried this myself yet but did you reboot the netboot.xyz server after changing the config? Maybe you just need to restart one of its services after changing the config? I've tried to restart the Compose stack including rm -rf'ing the contents of the config directory and same result. I'll loop back on it after I find a work-around for the outstanding issues with IPv6 in iPXE.

kerem commented

Author

Owner

@nrvale0 commented on GitHub (Aug 19, 2024):

I was able to work around the iPXE IPv6 oddities. I'm still not getting bootstrap from the cached Local Assets (ex: Debian 12*) even when live_endpoint is set and Docker Compose stack has been restarted. I'll see if I can find a log file somewhere just in case I have not specified the URL correctly and it is then falling back to the list in the GH repo.

@nrvale0 commented on GitHub (Aug 19, 2024): I was able to work around the iPXE IPv6 oddities. I'm still not getting bootstrap from the cached Local Assets (ex: Debian 12*) even when live_endpoint is set and Docker Compose stack has been restarted. I'll see if I can find a log file somewhere just in case I have not specified the URL correctly and it is then falling back to the list in the GH repo.

kerem commented

Author

Owner

@tgechev commented on GitHub (Dec 21, 2024):

I know this is old, but by chance if found the key point to getting local assets working.
On dashboard, edit boot.cfg, and set live_endpoint to your docker server address. Then netboot will look there for files.
https://netboot.xyz/docs/docker#local-mirror-access

I stumbled on the same issue and just wanted to confirm that this approach works. The only thing to check is the actual port to which port 80 is mapped in the container. I think the default is 8080 since that is what I had set up and I don't remember changing any ports when installing the container.

Another point to note is that once this URL is changed netboot will check the local assets only. It won't fallback to the netboot github URL.

@tgechev commented on GitHub (Dec 21, 2024): > > I know this is old, but by chance if found the key point to getting local assets working. > > On dashboard, edit boot.cfg, and set live_endpoint to your docker server address. Then netboot will look there for files. > > https://netboot.xyz/docs/docker#local-mirror-access > > ![image](https://private-user-images.githubusercontent.com/50232595/333562385-da832a57-431d-4212-b7aa-4d5d9b802b2a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzQ3NjkyNDEsIm5iZiI6MTczNDc2ODk0MSwicGF0aCI6Ii81MDIzMjU5NS8zMzM1NjIzODUtZGE4MzJhNTctNDMxZC00MjEyLWI3YWEtNGQ1ZDliODAyYjJhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEyMjElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMjIxVDA4MTU0MVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWUxMTUxMGM5YjViZTEyYThiNjc3NGJkMjBkZWM5YjA1ZTYxY2YyOTg2ZDI4YzhhZmEzYzljNmE5ZDI5ZTk3Y2YmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.-6PRzbzQU3fHJF_Dk3WybzkL5pmDemZ-NvQzQg5u42M) > > ![image](https://private-user-images.githubusercontent.com/50232595/333562680-55967d65-0721-43a9-b8ef-ef045014dd8a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzQ3NjkyNDEsIm5iZiI6MTczNDc2ODk0MSwicGF0aCI6Ii81MDIzMjU5NS8zMzM1NjI2ODAtNTU5NjdkNjUtMDcyMS00M2E5LWI4ZWYtZWYwNDUwMTRkZDhhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEyMjElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMjIxVDA4MTU0MVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWE3MTM0MGRkOTA1MjNjZDM3MDdmYjQ4OWQ2ZmU3NDE1NWEyM2RkMDIzNDMwNGFkMjg1NDUwYmIyYWEwYzA2ZGImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.xqjR-QR1pT--pnOWhB4mSU24vIbAKjQIy1wCd532OmA) I stumbled on the same issue and just wanted to confirm that this approach works. The only thing to check is the actual port to which port `80` is mapped in the container. I think the default is `8080` since that is what I had set up and I don't remember changing any ports when installing the container. Another point to note is that once this URL is changed netboot will check the local assets only. It won't fallback to the netboot github URL. ![image](https://github.com/user-attachments/assets/a08fc176-2ab3-49b3-80cd-7840110b1f15) ![image](https://github.com/user-attachments/assets/957d5694-978f-4ad3-a315-abc39465321e)

kerem commented

Author

Owner

@danboid commented on GitHub (Dec 21, 2024):

Another point to note is that once this URL is changed netboot will check the local assets only. It won't fallback to the netboot github URL.

Aha! So thats the real issue here then. netboot.xyz needs to be fixed so that it can use both local and online images simultaneously.

@danboid commented on GitHub (Dec 21, 2024): > Another point to note is that once this URL is changed netboot will check the local assets only. It won't fallback to the netboot github URL. Aha! So thats the real issue here then. netboot.xyz needs to be fixed so that it can use both local and online images simultaneously.

kerem commented

Author

Owner

@ilium007 commented on GitHub (Feb 18, 2025):

Just lost an hour of my life to this. Would help,if this doco page found via Google wasn't a broken link: https://netboot.xyz/docs/docker

Modifying boot.cfg with a local live_endpoint and restarting the docker container has zero effect on netBoot.xyz going to the internet vs using locally downloaded assets.

@ilium007 commented on GitHub (Feb 18, 2025): Just lost an hour of my life to this. Would help,if this doco page found via Google wasn't a broken link: https://netboot.xyz/docs/docker Modifying boot.cfg with a local live_endpoint and restarting the docker container has zero effect on netBoot.xyz going to the internet vs using locally downloaded assets.

kerem commented

Author

Owner

@tuxpowered commented on GitHub (Feb 24, 2025):

Same here, docker (installed via truenas scale) version 2.0.85

# set location of custom netboot.xyz live assets, override in local-vars.ipxe
isset ${live_endpoint} || set live_endpoint https://github.com/netbootxyz

Stock config lines 13-14 state to override live_endpoint in local-vars.ipxe.
Creating the local-vars.ipxe menu and adding set live_endpoing http://10.10.10.10:31011 Save config and boot test node still seeing the requests go out to the internet.

Commenting out line 14 (isset) and adding set live_endpoing http://10.10.10.10:31011 under it, save config, try again. No changes still goes out to internet.

Restart container, full stop, full start, retest - same thing still pulls from public internet.
Verified config files created on disk show the changes made. However they do not get used.

Yes: the live_endpoint is reachable and shows pulled assets.
No: the local-vars.ipxe file is detected on application start up.
(exiting to iPXE shell and executing echo ${live_endpoint} shows the default github url.)

Manually via ipxe setting the variable to the desired destination does work but it refuses to read it from the boot.cfg or load the local-vars.ipxe

@tuxpowered commented on GitHub (Feb 24, 2025): Same here, docker (installed via truenas scale) version 2.0.85 ``` # set location of custom netboot.xyz live assets, override in local-vars.ipxe isset ${live_endpoint} || set live_endpoint https://github.com/netbootxyz ``` Stock config lines 13-14 state to override live_endpoint in local-vars.ipxe. Creating the `local-vars.ipxe` menu and adding `set live_endpoing http://10.10.10.10:31011` Save config and boot test node still seeing the requests go out to the internet. Commenting out line 14 (isset) and adding `set live_endpoing http://10.10.10.10:31011` under it, save config, try again. No changes still goes out to internet. Restart container, full stop, full start, retest - same thing still pulls from public internet. Verified config files created on disk show the changes made. However they do not get used. Yes: the live_endpoint is reachable and shows pulled assets. No: the local-vars.ipxe file is detected on application start up. (exiting to iPXE shell and executing `echo ${live_endpoint}` shows the default github url.) Manually via ipxe setting the variable to the desired destination does work but it refuses to read it from the boot.cfg or load the local-vars.ipxe

kerem commented

https://github.com/netbootxyz/netboot.xyz/blob/master/roles/netbootxyz/templates/local-vars.ipxe.j2

Author

Owner

@systemdbrew commented on GitHub (Mar 27, 2025):

Same here, docker (installed via truenas scale) version 2.0.85
# set location of custom netboot.xyz live assets, override in local-vars.ipxe
isset ${live_endpoint} || set live_endpoint https://github.com/netbootxyz
Stock config lines 13-14 state to override live_endpoint in local-vars.ipxe. Creating the local-vars.ipxe menu and adding set live_endpoing http://10.10.10.10:31011 Save config and boot test node still seeing the requests go out to the internet.

Commenting out line 14 (isset) and adding set live_endpoing http://10.10.10.10:31011 under it, save config, try again. No changes still goes out to internet.

Restart container, full stop, full start, retest - same thing still pulls from public internet. Verified config files created on disk show the changes made. However they do not get used.

Yes: the live_endpoint is reachable and shows pulled assets. No: the local-vars.ipxe file is detected on application start up. (exiting to iPXE shell and executing echo ${live_endpoint} shows the default github url.)

Manually via ipxe setting the variable to the desired destination does work but it refuses to read it from the boot.cfg or load the local-vars.ipxe

Create page from "Menus" menu, call it "local-vars.ipxe". Paste in the template file linked in this comment.

Uncomment line 17 "set live_endpoint http://<enter_your_ip:PORT>"

This works for me on truenas scale Fangtooth RC1

@systemdbrew commented on GitHub (Mar 27, 2025): > Same here, docker (installed via truenas scale) version 2.0.85 > > ``` > # set location of custom netboot.xyz live assets, override in local-vars.ipxe > isset ${live_endpoint} || set live_endpoint https://github.com/netbootxyz > ``` > > Stock config lines 13-14 state to override live_endpoint in local-vars.ipxe. Creating the `local-vars.ipxe` menu and adding `set live_endpoing http://10.10.10.10:31011` Save config and boot test node still seeing the requests go out to the internet. > > Commenting out line 14 (isset) and adding `set live_endpoing http://10.10.10.10:31011` under it, save config, try again. No changes still goes out to internet. > > Restart container, full stop, full start, retest - same thing still pulls from public internet. Verified config files created on disk show the changes made. However they do not get used. > > Yes: the live_endpoint is reachable and shows pulled assets. No: the local-vars.ipxe file is detected on application start up. (exiting to iPXE shell and executing `echo ${live_endpoint}` shows the default github url.) > > Manually via ipxe setting the variable to the desired destination does work but it refuses to read it from the boot.cfg or load the local-vars.ipxe https://github.com/netbootxyz/netboot.xyz/blob/master/roles/netbootxyz/templates/local-vars.ipxe.j2 Create page from "Menus" menu, call it "local-vars.ipxe". Paste in the template file linked in this comment. Uncomment line 17 "set live_endpoint http://<enter_your_ip:PORT>" This works for me on truenas scale Fangtooth RC1

kerem commented

Author

Owner

@molnarti commented on GitHub (Aug 26, 2025):

is my understanding correct, that to boot local assets, i need to have the live_endpoint set to the local address AND have all the assets downloaded? e.g. there is no fallback to the assets on github? the diagram here https://netboot.xyz/docs/docker/ seems to tell othwrwise, but with the live_endpoint value set to github the local assets are not used, and when i set it to my local address then i need to have all assets downloaded.

also, is there a checksum check for the local assets? i was pulling out my here because the assets refused to boot, only to realize the downloaded file was smaller by 300 MB than it should have been

@molnarti commented on GitHub (Aug 26, 2025): is my understanding correct, that to boot local assets, i need to have the live_endpoint set to the local address AND have all the assets downloaded? e.g. there is no fallback to the assets on github? the diagram here https://netboot.xyz/docs/docker/ seems to tell othwrwise, but with the live_endpoint value set to github the local assets are not used, and when i set it to my local address then i need to have all assets downloaded. also, is there a checksum check for the local assets? i was pulling out my here because the assets refused to boot, only to realize the downloaded file was smaller by 300 MB than it should have been

kerem commented

Author

Owner

@rpi-maker commented on GitHub (Sep 5, 2025):

Same here, docker (installed via truenas scale) version 2.0.85
# set location of custom netboot.xyz live assets, override in local-vars.ipxe
isset ${live_endpoint} || set live_endpoint https://github.com/netbootxyz
Stock config lines 13-14 state to override live_endpoint in local-vars.ipxe. Creating the local-vars.ipxe menu and adding set live_endpoing http://10.10.10.10:31011 Save config and boot test node still seeing the requests go out to the internet.

Commenting out line 14 (isset) and adding set live_endpoing http://10.10.10.10:31011 under it, save config, try again. No changes still goes out to internet.

Restart container, full stop, full start, retest - same thing still pulls from public internet. Verified config files created on disk show the changes made. However they do not get used.

Yes: the live_endpoint is reachable and shows pulled assets. No: the local-vars.ipxe file is detected on application start up. (exiting to iPXE shell and executing echo ${live_endpoint} shows the default github url.)

Manually via ipxe setting the variable to the desired destination does work but it refuses to read it from the boot.cfg or load the local-vars.ipxe

Followed @systemdbrew comments to create "local-vars.ipxe" and reference local ip:port for netboot xyz assets. Tested to see if this would pull pre-downloaded assets (local self-hosted images) and verified that it initially starts to load the local assets, but then goes out to the internet anyway to re-pull the same image..

Not sure why Netboot XYZ is ignoring the local self-hosted only option, as it used to work with older versions of Netboot XYZ. Currently running version 2.0.88

@rpi-maker commented on GitHub (Sep 5, 2025): > Same here, docker (installed via truenas scale) version 2.0.85 > > ``` > # set location of custom netboot.xyz live assets, override in local-vars.ipxe > isset ${live_endpoint} || set live_endpoint https://github.com/netbootxyz > ``` > > Stock config lines 13-14 state to override live_endpoint in local-vars.ipxe. Creating the `local-vars.ipxe` menu and adding `set live_endpoing http://10.10.10.10:31011` Save config and boot test node still seeing the requests go out to the internet. > > Commenting out line 14 (isset) and adding `set live_endpoing http://10.10.10.10:31011` under it, save config, try again. No changes still goes out to internet. > > Restart container, full stop, full start, retest - same thing still pulls from public internet. Verified config files created on disk show the changes made. However they do not get used. > > Yes: the live_endpoint is reachable and shows pulled assets. No: the local-vars.ipxe file is detected on application start up. (exiting to iPXE shell and executing `echo ${live_endpoint}` shows the default github url.) > > Manually via ipxe setting the variable to the desired destination does work but it refuses to read it from the boot.cfg or load the local-vars.ipxe Followed @systemdbrew comments to create "local-vars.ipxe" and reference local ip:port for netboot xyz assets. Tested to see if this would pull pre-downloaded assets (local self-hosted images) and verified that it initially starts to load the local assets, but then goes out to the internet anyway to re-pull the same image.. Not sure why Netboot XYZ is ignoring the local self-hosted only option, as it used to work with older versions of Netboot XYZ. Currently running version 2.0.88

kerem commented

Author

Owner

@LinuxforPunks commented on GitHub (Oct 3, 2025):

I probably did not try all of these options but I did put live_endpoint into local-vars.ipxe, and even deleted anything resembling the default/online menu... and it still loaded the default/online menu. Over the last 10 days I've only been able to get this container to download images from the project, it won't use local assets at all and it nukes or ignores local configuration of boot.cfg, which it managed to do even with the container's bind-mount set to read-only in the docker-compose.yaml.

@rpi-maker which older versions of Netboot XYZ was it? If those are still online that would probably be fine for what I need. I don't even really need it to be dockerized so long as it's somewhat user-configurable

@LinuxforPunks commented on GitHub (Oct 3, 2025): I probably did not try all of these options but I did put live_endpoint into local-vars.ipxe, and even deleted anything resembling the default/online menu... and it still loaded the default/online menu. Over the last 10 days I've only been able to get this container to download images from the project, it won't use local assets at all and it nukes or ignores local configuration of boot.cfg, which it managed to do even with the container's bind-mount set to read-only in the docker-compose.yaml. @rpi-maker which older versions of Netboot XYZ was it? If those are still online that would probably be fine for what I need. I don't even really need it to be dockerized so long as it's somewhat user-configurable

kerem commented

Author

Owner

@LATINO-BICEPS commented on GitHub (Nov 29, 2025):

I want to note that with set live_endpoint http://x.x.x.x:8080 set in local-vars.ipxe, it does work but only for specific distributions. I suspect it is a variable substitution misconfiguration somewhere in the chain.

Linux Network Installs/
├── AlmaLinux ❌ pulls from repo
├── Debian ✅ pulls locally
└── Ubuntu ❌ pulls from repo

@LATINO-BICEPS commented on GitHub (Nov 29, 2025): I want to note that with `set live_endpoint http://x.x.x.x:8080` set in local-vars.ipxe, it does work but only for specific distributions. I suspect it is a variable substitution misconfiguration somewhere in the chain. ``` Linux Network Installs/ ├── AlmaLinux ❌ pulls from repo ├── Debian ✅ pulls locally └── Ubuntu ❌ pulls from repo ```

kerem commented