If you're attempting to start a workspace in a git based project, and are seeing failures in the Preparing stage, or just after the workspace appears to enter the Running stage, this usually indicates a problem accessing the git repo.
The execution.log in the support bundle (requires admin access) will contain important clues that validate there is a problem with access to the repo.
A successful checkout will show Domino preparing, cloning, checking out, and then cleaning the repo. This will be logged like the following screenshot:
If you see that this segment of the logs stops after preparing, and/or cloning, and then moving on to pulling the environment image, this is an indication that this process could not be completed. This may appear similar to the following screenshot:
In this scenario, check that you have the appropriate permissions either through your personal access token, or ssh key that allow you to access the repo. There could also be limitations on the repo itself that are preventing it from being checked out. In this specific scenario, the wrong repo had been added to the Domino project.
Here is a link to our documentation on setting up access to external repos, which includes the permissions you must have to the repo:
Also here is a link to finding the support bundle for workspaces so that you can access the execution log. You may have to request this from a Domino administrator if you're lacking admin access to Domino:
This is a common cause for issues starting workspaces in Domino projects with external repos, and in git based projects. If your findings differ, please open a support ticket with us, attaching the support bundle if you're able to access it, or request it. There is additional logging in the support bundle that will aid our analysis as we investigate the issue.
Please sign in to leave a comment.