Open LingHsiLiu opened 5 years ago
I am going to try to give a go at this.
Let's say you deployed a docker image on a remote machine somewhere. The typical use case is that you want your image to act as a server (providing some service) and to be deployed as an entity that performs its jobs without needing user inputs or rarely needing user inputs (i.e headlessly). If this is the typical use case of image and containers, then running graphical interfaces is not a feature built into them. Plus, on which screen would you have your graphical interface running? The infrastructure, to allow that to happen, do not come out of the box.
I think you need to run LabVIEW in containers, when your application provides some kind of service (some remote PXI somewhere acquiring some data and exposing that through some api). I also think that if this is possible, you might maybe want to look in the direction of remote accessing vis.
Note that the samples listed here don't need user interface. When user input is needed, it can be done via a command line client. (I guess it's also possible to create one to run with some headless LabVIEW Service)
That's just the opinion of someone new to containers and their world. Cheers.
I have a .exe for LabView sample. And, I already copy the sample to container. I tried to use "XXX.exe" to run the sample.
However, I couldn't see graphical interface for LabView. How do you know the sample run well and LabView runtime work well on container ?