The Instruqt platform currently assumes that the virtual machines in sandbox environments are Linux based. That means Windows support is limited.
What currently works:
Network connectivity between hosts, including DNS resolution based on host names defined in the environment configuration.
Injection of environment variables, that are defined in the environment configuration.
instruqt user with password
Passw0rd!, to facilitate interaction from others hosts in the environment.
What does NOT work yet:
Executing life cycle scripts directly on the Windows host.
Adding terminal/editor tabs for Windows hosts.
However, it is still possible to run Windows based images as part of sandbox environments. To interact with these images we support the following work-around:
Create a sandbox environment with two images; 1 Linux based, and 1 Windows based
The Windows VM will run your software.
The Linux VM is used as a proxy to the Windows VM for running life cycle scripts, and providing terminal access.
Create a Windows based VM image, that has:
Your software installed.
An SSH server (see https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse), that we can use to execute lifecycle scripts
A set of hard-coded credentials (username/password), that can be when executing scripts from the Linux VM, or use the automatically injected
Optional: If you need terminal support, either let users connect via an ssh command on the Linux VM, or install ttyd and expose that via a