New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GPU requirement and auto-detect NVIDIA extensions #173
GPU requirement and auto-detect NVIDIA extensions #173
Conversation
abece2b
to
b012c96
Compare
5bf01c3
to
5af8294
Compare
6dca834
to
dfc50d4
Compare
|
Hey @chrmarti just seen a lot of test failures on the CI - and slightly at a loss to understand what they mean and why they are failing. I'm happy to take a look, but I'm not sure what the difference between |
to support merging GPU requirements
aa7ef00
to
6772741
Compare
|
I've taken a bit of a closer look, and rebased onto the latest main - and I see the same failures running the tests locally, so I don't think this is a regression from this PR. |
|
@chris-major-improbable I have merged in the main branch and fixed an issue with the PR I found when looking into the test failures. Please check the above comment from the CLA bot, we must have added that after you submitted the PR. Thanks! |
|
@microsoft-github-policy-service agree [company="{Improbable Worlds Ltd}"] |
|
@microsoft-github-policy-service agree company="{Improbable Worlds Ltd}" |
|
@microsoft-github-policy-service agree company="Improbable Worlds Ltd" |
|
Thanks for that - looks good to me. |
This PR builds upon the proposal in devcontainers/spec#82
When launching a devcontainer requesting GPUs it also detects the presence of NVIDIA docker extensions, and adds the
--gpus allflag.This means that the same devcontainer can be used by developments that don't all have GPU's.
It also does the equivalent for docker-compose scripts, adding the GPU access to the service specified in the
devcontainer.jsonfile