Before creating your custom Docker image, make sure that the image you need is not already available on the Docker hub. To get started on building your own Docker image, head over to the Docker documentation.
See also this page for making the image available to Instruqt:
Our virtual machine images run on Google Cloud. To create your own vm image, head over to the Packer documentation. If you need some inspiration, you can browse our github organization and search for our packer repositories. If you need help, please reach out to us on Slack.
The Instruqt platform currently assumes that the virtual machines in sandbox environments are Linux based. That means our life cycle scripts and terminal/editor tabs will not work out of the box with Windows VMs.
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.
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
It depends! Since we base Instruqt around Linux, you can run most Linux based applications right on Instruqt. However, if you intend on running a Windows based application, this is currently possible, but only through a workaround. Please reach out to us by joining us on Slack so we can get you started.