mirror of
https://github.com/netbootxyz/netboot.xyz.git
synced 2026-04-25 07:05:56 +03:00
[GH-ISSUE #1601] Using Docker With Custom ISOs / Project Active? #2068
Labels
No labels
Hacktoberfest
Hacktoberfest
bootloader
bsd
bug
confirmed
documentation
duplicate
enhancement
enhancement
enhancement
eol
experimental-merged
freebsd
help wanted
invalid
investigate
ipxe
linux
live-os
memdisk
menu
no-issue-activity
no-issue-activity
pull-request
released
todo
upstream
windows
windows
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/netboot.xyz#2068
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ThePieMonster on GitHub (Mar 27, 2025).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1601
Hey @antonym, noticed a lot of issues pilling up. Is this project something you are still working on? Would be a good idea to look into having others help out and cleanup the repos.
That aside, new users are having trouble with the following such as trying to get their own ISO images to show up in the assets page for example.
https://github.com/netbootxyz/docker-netbootxyz/issues/24
https://github.com/netbootxyz/netboot.xyz/issues/1561
For the below, what are some examples of
-v config and assetsand how that can be used?Many people just want a solution that can host their own ISOs which can then be booted from via a PXE boot solution. Given that Docker is also something that is being forced to be used (since this doesn't have a Windows installation component) more detailed documentation should be provided around this.
https://netboot.xyz/docs/docker/parameters
@Firminator commented on GitHub (Mar 28, 2025):
What's with the recent influx of proposals to open-source projects to "help" with issues, or add additional devs, "cleanup" the repo, or financially help?
@jkoelker commented on GitHub (Mar 29, 2025):
https://en.wikipedia.org/wiki/XZ_Utils_backdoor
That said anyone is free to comment on bugs and try to reproduce or clean them up and report their findings, as well as send in PRs to add features, update documentation, or improve the project. OpenSource means not having to ask for permission to help, but after what we've seen happen, much caution needs to be taken with granting direct access for larger projects like this one.
@antonym commented on GitHub (Mar 29, 2025):
@ThePieMonster The project is open for anyone to contribute and make proposals and help out. My time is limited but I do strive to maintain and fix things when I can, but it's also a very tiny part of my day to day. This started out as a hobby, and I enjoy helping others learn a lot of the things I've learned over the years. I review PRs and suggestions when they make sense and I can knock them out in a reasonable amount of time.
One of the things I've tried to do with this project is make as much of it open and visible as possible, I think that's really the only way a project like this works. OS distributions change pretty rapidly and they tend to break pretty often especially with the large amount of tools and operating systems we support.
If you are looking to host a bunch of ISOs that are available at any moment, I'd suggest other tools to do so: https://netboot.xyz/docs/booting/iso#usb-bootable-virtual-media.
iPXE typically doesn't typically handle ISOs well, hence why we usually host vmlinuz and initrd assets or prefer Linux installer kernels. A lot of the newer ISOs are huge and almost go against the main benefit of using netboot.xyz to load a lightweight boot loader, load lightweight kernels, and then just stream down only the packages needed.
@ThePieMonster commented on GitHub (Mar 29, 2025):
@Firminator @jkoelker The concern is that someone could spend time contributing to a repository, create PR's, the PR's would just sit untouched, or comments unanswered by the single or few maintainers a repo has. Sure you could go and fork the repo and make your own version with your own commits, but more than likely that repo isn't going to be spotted by others as the original is always what shows up in the search results. I personally have students have for many times where someone makes a contribution and it just sits there. Even amazing contributions that fixed pretty large bugs will go unnoticed because the owner disappears. Hence, It is worth asking and confirming that the repository is active and there's going to be people, ideally more than one, that can be a maintainer of the repo so contributions are merged. It is irrelevant if the repository was active years ago, doesn't mean still going to be active today.
@antonym Thanks for the answer. Seems like what I might be looking for regarding ISOs could be another solution such as https://github.com/ventoy/PXE/releases (not actually open source however) then or a custom solution. Will continue to search.