Licensing for building in containers

[SimonRichter]

I have a working setup for compiling images inside a Docker container using QuartusII Lite, that is reasonably comfortable for simple designs.

Obviously, that would break for anything that requires licensed features or IP components, is there a mechanism I could use to make licenses available to containers that works with the constraints imposed by that, such as containers being created and torn down for each build with random MAC addresses on the virtual network interface?

Ideally I'd be able to spawn ten builds in parallel with different seeds and choose the image with the best timing, but for me it'd also be acceptable to run them sequentially over night.

[JohnT_Intel]

Hi,

If you are afraid of the IP that need license then I would recommend you to purchase license for that system for compilation. If my understanding is incorrect, please provide more detail information.

For parallel or sequential compilation, then you will need to rely on TCL scripting which you can refer to https://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/manual/tclscriptrefmnl.pdf.

[Rickard]

What about publishing a public docker image to Docker hub (https://hub.docker.com) with Light Ed installed? Would that violate the EULA? We would like to use it in a open source project for CI to verify changes to the Verilog part of the code.