Unable to build with remote linux device

I am unable to select a remote linux device that I can ssh into as a build device.

Having worked with a number of companies while working with professional services, I see many companies doing development in a linux VM, on a Windows host, deploying to a QNX target for example. Being able to use Qt Creator natively would be a big quality of life improvement if possible.

I do think this is a worthwhile improvement. Building a qt app within a VM might be a more common workflow than one would expect and it seems that right now, doing so also requires using qt creator in the VM which is not that great of an experience for a few reasons (not qt creator's fault, just limitations of running graphical apps in a vm). Personally I believe using a docker based development workflow would be better because the environment would be more tightly controlled. I think people resort to using VMs instead of docker because it is simpler to understand and more familiar, so I don't think VM based dev workflows are going to completely go away anytime soon.

Some comments from the internal conversation:

Basically the split of into a "backend part" in the container, and a "frontend part" on the host, is not possible with Qt Creator and is not planned to have, at least not as the primary approach to the problem, as it would restrict us to fairly beefy devices running the backend, which would not work for Qt for MCU etc.

There is ongoing work on an approach that let's you specify a "build device" and "run device" different from your host, which theoretically could solve the problem in a different way.

Currently we are focusing on implementing that for Docker though, and only "Desktop" (the local development host) and "Docker" are white-listed as build device.
​

The "development in a linux VM, on a Windows host, deploying to a QNX" is actually quite independent of that.  at least "development in a linux VM, on a Windows host" and "deploying from Linux to QNX" should actually work out of the box already. I don't think we've tried the combination, but there should be no conceptual extra problem.

The scenario  (S) "creator on windows host + toolchain in linux-vm-on-window" that this report asks for  would require a "remote linux" build device.  The following setups should work:  (1) "run the whole setup including creator in the linux-vm-on-window" (that's basically a "local linux host" as build device in the creator setup in the vm) ,  or (2) "run creator on the  windows host, but don't use a linux vm, but a docker container with linux" (that's "docker as build device").

The feature requested here should actually be achievable by not-so-heavy modifications in the code, but was so far not requested/needed. I can have a look if you want to