Enable TFTP and HttpBoot without caching boot files

Support
1

Problem:

Attempting to run Foreman in containers (Foreman UI and Foreman-Proxy). We are using custom Windows and Linux images and the only file that will be modified is the Windows boot.wim all other files we can pull directly from the ISO. Is there a way that when we do not cache the boot files when we start a build? This will save space on our disks that can be utilized for the ISO images.

Expected outcome:

Execute a build without caching boot files in tftpboot/boot

Foreman and Proxy versions:

Foreman: 3.16.0

Proxy: 3.16.0

Foreman and Proxy plugin versions:

No plugins installed

Distribution and version:

Other relevant data:

2

I’ll see if I can get a more firm response for you, but I do not think this is supported.

3

@lstejska might be able to help more here, but can you describe what you’re seeing a bit more with regards to the caching? Are there extra files in the tftpboot folder that you don’t need?
I wonder if you could just disable Foreman’s management of TFTP if you have a custom solution.

1 Like
4

Hi,
If you boot from the ISO and get all the data from it, you can do several things:

  • Disable tftp on the smart proxy
  • Unassign installation media from the OS (you probably don’t need it)
  • Make sure only templates for image-based provisioning are assigned to the OS.
1 Like