starred/netboot.xyz

Fork 0

mirror of https://github.com/netbootxyz/netboot.xyz.git synced 2026-04-25 23:25:54 +03:00

[GH-ISSUE #1125] Ubuntu live images fail to boot #1842

New issue

Closed

opened 2026-03-01 18:36:49 +03:00 by kerem · 4 comments

kerem commented

2026-03-01 18:36:49 +03:00

Owner

Originally created by @danboid on GitHub (Jun 13, 2022).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1125

I have set up a local instance of the latest netboot.xyz docker container Ubuntu 22.04 but I am unable to successfully boot any of the Ubuntu 22.04 and 20.04 live images. After netboot has downloaded one of the several Ubuntu live images, it seems to drop to BusyBox and I get the errors:

curl: (23) Failed writing body (0 != 1378)
Done.
Unable to find a live file system on the network

I am able to boot the normal Ubuntu install image from Netboot.xyz fine.

Originally created by @danboid on GitHub (Jun 13, 2022). Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1125 I have set up a local instance of the latest netboot.xyz docker container Ubuntu 22.04 but I am unable to successfully boot any of the Ubuntu 22.04 and 20.04 live images. After netboot has downloaded one of the several Ubuntu live images, it seems to drop to BusyBox and I get the errors: ``` curl: (23) Failed writing body (0 != 1378) Done. Unable to find a live file system on the network ``` I am able to boot the normal Ubuntu install image from Netboot.xyz fine.

kerem

2026-03-01 18:36:49 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-01 18:36:50 +03:00

Author

Owner

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

ATM (inc. in my PR) the path for the assets is marked as optional when really it should be stated as required else it breaks this feature which is one of the main advantages of setting up your own netboot server.

@danboid commented on GitHub (Jun 13, 2022): ATM (inc. in my PR) the path for the assets is marked as optional when really it should be stated as required else it breaks this feature which is one of the main advantages of setting up your own netboot server.

kerem commented

2026-03-01 18:36:50 +03:00

Author

Owner

@borekon commented on GitHub (Jun 24, 2022):

I tried several distros, and many of them won't boot with the same message

@borekon commented on GitHub (Jun 24, 2022): I tried several distros, and many of them won't boot with the same message

kerem commented

2026-03-01 18:36:50 +03:00

Author

Owner

@antonym commented on GitHub (Jun 25, 2022):

I wasn't getting this error with 8GB of RAM but once I switched it to 4GB, I begin getting a similar error.

curl: (23) Failed writing body (0 != 14216)
done.
Unable to find a live file system on the network.

I was testing with locally synced assets. The Live CDs are generally fatter and have to load more into memory. There may be some ramdisk_size settings that could be tuned but I would suggest feeding it more RAM and see what the result is.

Generally if you want to keep a lower memory footprint, the Linux Menu installers are generally the way to go, even though the Ubuntu network installer is now fatter than it used to be because it pulls the ISO down during boot.

If you want to load the full Live CD from the second menu, typically all of those will require more RAM. If it fails in the initrd section, more than likely it's either having a problem getting on the network or runs out of space when retrieving the rootfs.

@antonym commented on GitHub (Jun 25, 2022): I wasn't getting this error with 8GB of RAM but once I switched it to 4GB, I begin getting a similar error. ``` curl: (23) Failed writing body (0 != 14216) done. Unable to find a live file system on the network. ``` I was testing with locally synced assets. The Live CDs are generally fatter and have to load more into memory. There may be some ramdisk_size settings that could be tuned but I would suggest feeding it more RAM and see what the result is. Generally if you want to keep a lower memory footprint, the Linux Menu installers are generally the way to go, even though the Ubuntu network installer is now fatter than it used to be because it pulls the ISO down during boot. If you want to load the full Live CD from the second menu, typically all of those will require more RAM. If it fails in the `initrd` section, more than likely it's either having a problem getting on the network or runs out of space when retrieving the rootfs.

kerem commented

2026-03-01 18:36:50 +03:00

Author

Owner

@docseymour12-hash commented on GitHub (Sep 28, 2025):

Fix this pls

@docseymour12-hash commented on GitHub (Sep 28, 2025): Fix this pls

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/netboot.xyz#1842

No description provided.

Rows
Columns