oh i see what you’re doing wrong here, sorry. You need to unpack the ISO and make those contents available. Your best bet is to scroll down and find kubuntu and click download. You’ll get the correct data.
So what you are saying is I cannot utilize a ISO, I have to unpack an ISO and then I’ll be able to boot off it of it… Never tried to unpack an iso you recommend any special software…thanks in advance
basically, though it’s likely much more efficient to download the assets from within the system, but yes, the pxeloader environment has no clue what to do with an ISO image
just mount the iso in the assets folder and restart the netboot container
I am working on the same project, or at least similar. In my environment, we have been designing our own ISOs with Preseeding. My test scenario would be to run this container and build an Ansible command to start it up for any site that may need a device re-imaged.
Unfortunately, we have many sites running extremely slow speeds so that’s why we want to host the ISO locally.
I am a little confused when @driz said to unpack the ISO locally, or Mount it in that directory? Do you mean extract the contents of the ISO in my linked Assets directory? Or do you mean I can write a startup script that makes sure the ISO is mounted in my Linked Assets directory at all times?
I also see my ISO in my Untracked Assets, and don’t completely understand where I am suppose to find the ISO in the menu after I PXE boot.
in this case, you dont need to mess with the ISO, just look at your assets and tell it to download the debian version stuff you want, follow the netboot.xyz guidance (or our blog on netboot) for pointing locally
I have been following that guide, but the section where using Local Assets confuses me. I am trying to use it on a custom ISO I have, customized via Pre-seed. But it shows under Untracked Assets. I put the ISO into a location: /PXEassets, that was linked to the assets of the container.
