Links

FAQ

Questions about Instruqt?
You can find the available environment variables at /etc/profile.d/instruqt-env.sh
This is usually caused by your container or virtual machine running out of memory. Try increasing the memory and running your process again.
To use services running on HTTPS (including self-signed certificates), use a port that ends with 443. For example, you could use port 8443.
While the sandbox hosts are starting up, the Instruqt platform tries to make an SSH connection. You will see this in the logs:
Retrying SSH connection until it is available: ssh: handshake failed
This is expected behavior and it should not last more than 10-20 seconds until a connection is made.
The track logs show the cause, but most likely this is a permissions error as our service account needs access to use your machine image.
Container images built using podman or buildah might not work properly. Sometimes tracks using those images won't start, and instruqt track logs shows a message like this one:
2020-12-04T12:50:31Z bii3rgpaqgcr INFO: module.hostname.kubernetes_deployment.deployment: Still creating... [1m0s elapsed]
To resolve this issue, use the option --format=docker to push to the registry. The underlying problem is that the mediaType in the container image is not set properly, causing the Kubernetes pod to fail with the following error:
Error response from deamon: mediaType in manifest should be 'application/vnd.docker.distribution.manifest.v2+json' not ''
Do you still have questions? Join our Slack and let us know how we can help you!