-
Notifications
You must be signed in to change notification settings - Fork 330
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
Devcontainer GPU support #945 #946
Devcontainer GPU support #945 #946
Conversation
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
a10e042
to
bf41d4b
Compare
You need to sign the CLA |
Hi @bhack I signed. |
.devcontainer/devcontainer.json
Outdated
@@ -32,6 +32,12 @@ | |||
"version": "os-provided" | |||
} | |||
}, | |||
|
|||
// Uncomment this if GPU support it is required |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NIT:
probably we could remove "it" also in the previous string.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure thing, I'll also update the top comment to reflect the same:
"// Uncomment this if GPU support is required"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is ok for me.. we cannot test this in the CI cause it would require to run in cloudbuild as Gtihub Actions are CPU only.
But as it is commented by default as the other "optional" entry related to the GPU tensorflow docker image it is ok for me.
I also tested this locally and the container spun up properly with GPU access verified via:
|
Thanks |
/cc @LukeWood I don't have the permission to kickstart the CI workflows, please start the CI jobs. |
It don't know if you want to add a reference to microsoft/vscode-remote-release#3972 in the source comments. So that we could have a reminder to imporve this when we will have a little bit of scripting support instead of requiring to the developer to comment and uncomment multiple sections just to switch from cpu to gpu and back. |
Good idea! I'll add a reference tomorrow morning 👍🏻 (it's evening here now) |
.devcontainer/devcontainer.json
Outdated
// TODO: Improve to allow dynamic runArgs, see microsoft/vscode-remote-release#3972 | ||
// Uncomment this if GPU support is required | ||
// "runArgs": [ | ||
// "--gpus=all" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: can you align this comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, that seemed to do the trick. :)
/gcbrun |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR!
No problem, thanks for the accept and the great work you guys are doing. |
* update devcontainer * update comment * todo added to improve runargs * Aligned comment.
What does this PR do?
A small update to devcontainer.json to enable GPU support. Added "RunArgs" to devcontainer.json.
Fixes issue 945
Before submitting
Pull Request section?
to it if that's the case.
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.