So I'm going to start a thread to post what I'm learning, and wanted to stop derailing this thread: LabVIEW-Continuous-Integration-License. Hopefully the contents of that thread indicate that it should be more possible to build your own container and license it without a service request, even without VLM, but I haven't yet confirmed that for myself (and Felipe makes it sound unlikely, although maybe he was misunderstanding what I'd written). My first enjoyable finding is that "nipkg pack" now works in windows/servercore:2004. I don't know if something changed in NIPM 21.0.0 (or potentially a couple of previous versions, I last tried with 20.5 in windows:1909), or if this is due to some update in the Microsoft images, but this is very useful for writing a Dockerfile that can create its own fake packages. A list of packages (not updated for 2021) that I faked previously, for the cRIO build demo at GLA Summit, is as follows: ni-cabled-pcie ni-controllerdriver ni-ede ni-pxiplatformservices-runtime ni-rio-fpga-driver ni-rio-mite ni-serial-runtime ni-usblan ni-usbvcp ni-visa-shared-components I'll check through and see if any of these became more installable without fakes, but if not, they can now be easily recreated. It's possible that other packages might also need to be faked, depending on what you're trying to install in the end... Something to note in this endeavour is that not all packages have a version 21.*, presumably due to varying update cycles for different drivers. So pattern matching on version 21.* using nipkg info can be a problem (for example, it seems like version 19.0.0.49153-0+f1 is the latest ni-usblan).The feeds I'm currently using for 2021 are generated as follows: # This script adds feeds to nipkg for a specific build set # Here we focus on LabVIEW 2021, 32-bit. $year = "2021" $pkg_root = "https://download.ni.com/support/nipkg/products" $lv_modules = "rt-module", "fpga-module", "vi-analyzer-toolkit", "aspt-toolkit", "cdsim-module", "mathscript-module" # The "core" modules don't include core in the URL nipkg.exe feed-add --name="""ni-labview-$year-core-x86-en-$year-released""" --system $("$pkg_root/ni-l/ni-labview-$year-x86/21.0/released") nipkg.exe feed-add --name="""ni-labview-$year-core-x86-en-$year-released-critical""" --system $("$pkg_root/ni-l/ni-labview-$year-x86/21.0/released-critical") # The other ni-l/ni-labview-... packages have a shared pattern ForEach($module in $lv_modules) { nipkg.exe feed-add --name="""ni-labview-$year-$module-x86-en-$year-released""" --system $("$pkg_root/ni-l/ni-labview-$year-$module-x86/21.0/released") nipkg.exe feed-add --name="""ni-labview-$year-$module-x86-en-$year-released-critical""" --system $("$pkg_root/ni-l/ni-labview-$year-$module-x86/21.0/released-critical") } $feeds = @( [pscustomobject]@{name = "ni-daqmx-21-0-released"; url = "$($pkg_root)/ni-d/ni-daqmx/21.0/released"} [pscustomobject]@{name = "ni-visa-21-0-released"; url = "$($pkg_root)/ni-v/ni-visa/21.0/released"} [pscustomobject]@{name = "ni-compactrio-21-0-released"; url = "$($pkg_root)/ni-c/ni-compactrio/21.0/released"} ) ForEach($pair in $feeds) { nipkg.exe feed-add --name="""$($pair.name)""" --system $($pair.url) nipkg.exe feed-add --name="""$($pair.name)-critical""" --system $($pair.url + "-critical") } You can see the names of the main modules in the "$lv_modules" variable, there is also the "core" feed and each has a -critical version too (although I don't know if these matter for Docker so much...) DAQmx, VISA and CompactRIO have a slightly different naming pattern, so they're handled separately at the bottom of that script, which I copy into my container and then run to add the feeds. As can be seen, nipkg is on my PATH to be able to run these more easily.

Continuous Integration

Information re LabVIEW (2021) in Docker containers

Christian,

Have you looked at this link on NIs site?

It seems to describe a command line option you can run against the Licensing application and provide a serail number to get the licensing done siilently and automatically.

Bill Welch

Message 11 of 11

(1,003 Views)

Continuous Integration

Information re LabVIEW (2021) in Docker containers

Re: Information re LabVIEW (2021) in Docker containers