tftp boot installer and PXE server container image
an invention by kukuk
Updated almost 5 years ago. 1 hackers ♥️. 1 follower.

We provide tftp server and RPMs containing the installer to run from tftp. Disadvantage is, that the user needs to setup a tftp boot system first. Why not putting everything in a container, so that the admin only need to run the container and can then choose on the to be installed machine, what he wants install? And following this, put the container in a kubernetes cluster like SUSE CaaS Platform.

There are two images:

  • opensuse-tftp-installer - this image only contains a tftp daemon, the DHCP server needs to point to this server. This container image only needs port 69.

  • opensuse-pxe-server - this image uses dnsmasq as PXE server, no changes to an existing DHCP server are necessary. This container image needs full access to the host network.

OBS project

Github project

Looking for hackers with the skills:

Nothing? Add some keywords!

This project is part of:

Hack Week 17

Activity

  • almost 6 years ago: gary_lin liked this project.
  • almost 6 years ago: kukuk started this project.
  • almost 6 years ago: kukuk originated this project.


    • Comments

    • mwilck
      almost 6 years ago by mwilck | Reply

      Isn't this mainly useful in connection with a PXE server? Then the PXE server needs to know about the container... A dnsmasq container could combine PXE and tftp functionality, but it might be unwelcome in managed environments.

      • kukuk
        almost 6 years ago by kukuk | Reply

        Yes, you need a dhcp server somewhere, which points the client to the tftpd installer container. You can of course create an own container for this, but the configuration efford is much higher.

      • StefanBruens
        almost 6 years ago by StefanBruens | Reply

        PXE and address allocation using DHCP are largely independent, i.e. you can get the address from the company DHCP server and the bootserver information from your own DHCP server. This is proxyDHCP.

        For this to work, you need a DHCP client which really adheres to the spec. It should broadcast a DISCOVER, collect OFFERs for 5 seconds, select one of the offers and continue. For PXE, it should select two OFFERs, one for the address and one for the boot server. It should use the first one to configure its address, and then use the second one to contact the boot server.

    • kukuk
      almost 6 years ago by kukuk | Reply

      I also created a PXE server image now.

    Similar Projects

    This project is one of its kind!