Could not boot: No such file or directory (https://ipxe.org/2d02803b)

[Mikec78660]

[]: This bug persists when memory is increased beyond 8GB.

verified

Describe the bug
I am using netboot.xyz under runtipi in a docker container, in an lxc in proxmox. I have a strange issue. if I let the boot process happen normally I get the menu as expected. No matter the distro or live cd I choose I get what appears to be a DNS error stating:
network unreachable (https://ipxe.org/280a6011)
could not boot: Network unreachable (https://ipxe.org/280a6011)
Could not boot: No such file or directory (https://ipxe.org/2d02803b)
Error occurred, press any key to return to the menu ...

So it would seem like I have a DNS issue. But if I press m at the boot process and go to manual netowrk configuration and just press enter to accept all the defaults I can boot any image just fine. If I let it boot normally and check the DNS server it lists my pihole server running at 192.168.0.4 but will not load images. but when I do the manual network setup it pre fills 192.168.0.4 and I just hit enter and it works fine. I can't figure out why this is happening.

To Reproduce
Steps to reproduce the behavior:

1. let the machine boot to pxe server, get the menu, select an image and get the errors mentioned above.

Expected behavior

1. let the machine boot, select the image and have the image load and boot.

[strobit]

I have the exact same issue. I configured everything for the first time 3 weeks ago, working like a charm.
Tried it yesterday on a laptop, and could not get it to work.
Debugged for hours, and just like you said, using manual network configuration works, no issues.

I am running netboot.xyz in a docker compose container, on a openmediavault server.
My router is running pfSense.

[Mikec78660]

Weird with the exception of running it in a docker container our setups seem really different but we are seeing the same issue.