-
Notifications
You must be signed in to change notification settings - Fork 67
install selector: Drop python 3.9 for nightlies, default to CUDA 12.5 for stable and nightly #534
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -370,7 +370,7 @@ | |
| active_python_ver: "3.11", | ||
| active_conda_cuda_ver: "12", | ||
| active_pip_cuda_ver: "12", | ||
| active_docker_cuda_ver: "12.2", | ||
| active_docker_cuda_ver: "12.5", | ||
| active_method: "Conda", | ||
| active_release: "Stable", | ||
| active_img_type: "Base", | ||
|
|
@@ -380,9 +380,11 @@ | |
|
|
||
| // all possible values | ||
| python_vers: ["3.9", "3.10", "3.11"], | ||
| python_vers_stable: ["3.9", "3.10", "3.11"], | ||
| python_vers_nightly: ["3.10", "3.11"], | ||
| conda_cuda_vers: ["11", "12"], | ||
| pip_cuda_vers: ["11.4 - 11.8", "12"], | ||
| docker_cuda_vers: ["11.8", "12.0", "12.2", "12.5"], | ||
| docker_cuda_vers: ["11.8", "12.0", "12.5"], | ||
|
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 12.5 images have been available since 24.08: rapidsai/docker#689 12.2 images will be dropped in 24.10: rapidsai/docker#696
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm proposing just unconditionally dropping 12.2 for simplicity and to nudge people towards newer images. But if reviewers disagree, I'd be happy to introduce a similar structure to what I'm proposing for Python versions, that allows the CUDA versions to differ by release. I think that'd be generically useful, just didn't add it here to limit the size of this PR. |
||
| methods: ["Conda", "pip", "Docker"], | ||
| releases: ["Stable", "Nightly"], | ||
| img_loc: ["NGC", "Dockerhub"], | ||
|
|
@@ -708,6 +710,11 @@ | |
| }, | ||
| disableUnsupportedPython(python_version) { | ||
| var isDisabled = false; | ||
| if (this.active_release === "Stable") { | ||
| isDisabled = !this.python_vers_stable.includes(python_version) | ||
| } else if (this.active_release === "Nightly") { | ||
| isDisabled = !this.python_vers_nightly.includes(python_version) | ||
| } | ||
| return isDisabled; | ||
| }, | ||
| disableUnsupportedImgType(type) { | ||
|
|
@@ -733,6 +740,18 @@ | |
| releaseClickHandler(e, release) { | ||
| if (this.isDisabled(e.target)) return; | ||
| this.active_release = release; | ||
|
|
||
| /* | ||
| It's possible that the active Python version prior to someone changing releases | ||
| isn't supported by whatever release was chosen in the selector. | ||
|
|
||
| This handles that case, updating to the oldest Python version supported by the chosen release. | ||
| */ | ||
| if (this.active_release === "Stable" && !this.python_vers_stable.includes(this.active_python_ver)) { | ||
| this.active_python_ver = this.python_vers_stable[0]; | ||
| } else if (this.active_release === "Nightly" && !this.python_vers_nightly.includes(this.active_python_ver)) { | ||
| this.active_python_ver = this.python_vers_nightly[0]; | ||
| } | ||
| }, | ||
| imgTypeClickHandler(e, type) { | ||
| if (this.isDisabled(e.target)) return; | ||
|
|
||
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.
Following these testing steps as documented worked... but only the first time.
This command leaves behind a
_site/directory with file permissions showing the default user inside the container as the owner. Where that user differs from the default user on the system where you rundocker run, the second attempt to run this fails like this:Removing that directory at startup every time avoids that tiny bit of development friction.