Setup-a-Windows-OVH-instance-for-CI.md

@@ -113,3 +113,19 @@ Troubleshooting
 `ERROR: Job failed: failed to pull image "buildtools" with specified policies [always]: Error response from daemon: pull access denied for buildtools, repository does not exist or may require 'docker login': denied: requested access to the resource is denied (manager.go:237:1s)`
 
   Did you add `pull_policy = ["if-not-present", "always"]` in the `[runners.docker]` section of the `C:\GitLab-Runner\config.toml` file?
+
+
+
+Debug inside Docker
+===================
+
+It may be necessary to run commands inside the Docker to understand why the CI fails. In order to do so, connect to the server and run `docker run -v C:/:C:/C -it buildtools`. With this command, you will have access to the `C:\` driver of the server inside the `C:\C\` folder in the container. This way, you may download for example build artifacts in the server and access them inside the Docker to re-run the failing commands.
+
+You will need to first execute in the docker the commands in the `before_script` section from the failing YML CI file, in order to setup the environment requirements.
+
+To check if there is some DLL missing, use this kind of command in the Docker:
+
+```
+& 'C:\Program Files\Git\bin\bash.exe' -c 'C:/builds/eclipse/aidge/aidge_core/build_cpp/unit_tests/Debug/tests_aidge_core.exe'
+```
+