Set web proxy to fetch assets?

[jkotran]

Hello there,

How do I set a web proxy for the netboot.xyz container to fetch assets, etc? I'm on a network where I cannot bypass a mandatory web proxy. Does netboot.xyz delegate fetch/download tasks to tools like curl/wget? Can I simply pass http_proxy/https_proxy environment variables to the container at startup?

Best,

Joe Kotran

[ItMeCorban]

Would love an answer to this. Running on a corporate network and servers don't have direct internet access for obvious reasons. Trying to install debian I get "connection timed out" on the install screen because at no point has it asked me for an outbound proxy. Setting the container environment variables for http_proxy didn't seem to make any difference.

[jkotran]

Hey, I've since learned that we can use something called a Docker sidecar to provide proxy access to a container. It's probably best to go that way.

https://hub.docker.com/r/xavierlam/proxy-sidecar

[NiKiZe]

iPXE does not support any proxy, if it can't reach the internet hosted variants you should probably setup a local cache, or just have the DNS record point to your proxy if it supports transparent forward. (of course no https in that case)
When it comes to when any OS has booted, such as the debian installer etc, you need to check that distributions specific values..

But I must ask, so the clients can't reach any web, however if you know the proxy address they suddenly can? What is the reasoning that makes that setup safer in any way? (there of-course is ways that it can be, such as username/password or packet inspection, but that can be achieved with captive portal, 802.1x or just packet inspection)

[jkotran]

Hi, my aim is to proxy the Internet downloads, such as iso files. Endpoints I'm provisioning will not be proxied to my on-site netboot.xyz instance.