Skip to content
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

[Release Test] Update cuda version in gpu docker cluster launcher image to 12.1 #42246

Merged

Conversation

architkulkarni
Copy link
Contributor

@architkulkarni architkulkarni commented Jan 8, 2024

Why are these changes needed?

After the Ray 2.9 release, the release test for the GPU Docker example cluster YAML file started failing with

2023-12-23 03:00:43,078 VINFO command_runner.py:371 -- Running `docker run --rm --name ray_nvidia_docker -d -it  -e LC_ALL=C.UTF-8 -e LANG=C.UTF-8 --shm-size='2301055426.56b' --runtime=nvidia --net=host rayproject/ray:latest-gpu bash`
24897079968c098daccf1ed65a0bea5d3d9e3df84de201ea20f1a34b0363975c
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: requirement error: unsatisfied condition: cuda>=11.8, please update your driver to a newer version, or use an earlier cuda container: unknown.

The likely cause is Ray 2.9 increased the required CUDA version to 11.8. This PR updates the CUDA version used in the GCP VM image in the example cluster YAML file from 11.3 to 12.1. The test passes after this change.

Related issue number

Closes #42134

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

@architkulkarni architkulkarni marked this pull request as ready for review January 9, 2024 00:27
@architkulkarni
Copy link
Contributor Author

Release test running here: https://buildkite.com/ray-project/release/builds/5418

Assigning @stephanie-wang as core-oncall (codeowner) as Hongchao is out.

@architkulkarni
Copy link
Contributor Author

@architkulkarni architkulkarni merged commit 4d0f6dd into ray-project:master Jan 10, 2024
9 checks passed
architkulkarni added a commit to architkulkarni/ray that referenced this pull request Jan 10, 2024
…ge to 12.1 (ray-project#42246)

After the Ray 2.9 release, the release test for the GPU Docker example cluster YAML file started failing with

2023-12-23 03:00:43,078 VINFO command_runner.py:371 -- Running `docker run --rm --name ray_nvidia_docker -d -it  -e LC_ALL=C.UTF-8 -e LANG=C.UTF-8 --shm-size='2301055426.56b' --runtime=nvidia --net=host rayproject/ray:latest-gpu bash`
24897079968c098daccf1ed65a0bea5d3d9e3df84de201ea20f1a34b0363975c
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: requirement error: unsatisfied condition: cuda>=11.8, please update your driver to a newer version, or use an earlier cuda container: unknown.
The likely cause is Ray 2.9 increased the required CUDA version to 11.8. This PR updates the CUDA version used in the GCP VM image in the example cluster YAML file from 11.3 to 12.1. The test passes after this change.

Related issue number
Closes ray-project#42134

---------

Signed-off-by: Archit Kulkarni <[email protected]>
architkulkarni added a commit to architkulkarni/ray that referenced this pull request Jan 10, 2024
…ge to 12.1 (ray-project#42246)

After the Ray 2.9 release, the release test for the GPU Docker example cluster YAML file started failing with

2023-12-23 03:00:43,078 VINFO command_runner.py:371 -- Running `docker run --rm --name ray_nvidia_docker -d -it  -e LC_ALL=C.UTF-8 -e LANG=C.UTF-8 --shm-size='2301055426.56b' --runtime=nvidia --net=host rayproject/ray:latest-gpu bash`
24897079968c098daccf1ed65a0bea5d3d9e3df84de201ea20f1a34b0363975c
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: requirement error: unsatisfied condition: cuda>=11.8, please update your driver to a newer version, or use an earlier cuda container: unknown.
The likely cause is Ray 2.9 increased the required CUDA version to 11.8. This PR updates the CUDA version used in the GCP VM image in the example cluster YAML file from 11.3 to 12.1. The test passes after this change.

Related issue number
Closes ray-project#42134

---------

Signed-off-by: Archit Kulkarni <[email protected]>
vickytsang pushed a commit to ROCm/ray that referenced this pull request Jan 12, 2024
…ge to 12.1 (ray-project#42246)

After the Ray 2.9 release, the release test for the GPU Docker example cluster YAML file started failing with

2023-12-23 03:00:43,078 VINFO command_runner.py:371 -- Running `docker run --rm --name ray_nvidia_docker -d -it  -e LC_ALL=C.UTF-8 -e LANG=C.UTF-8 --shm-size='2301055426.56b' --runtime=nvidia --net=host rayproject/ray:latest-gpu bash`
24897079968c098daccf1ed65a0bea5d3d9e3df84de201ea20f1a34b0363975c
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: requirement error: unsatisfied condition: cuda>=11.8, please update your driver to a newer version, or use an earlier cuda container: unknown.
The likely cause is Ray 2.9 increased the required CUDA version to 11.8. This PR updates the CUDA version used in the GCP VM image in the example cluster YAML file from 11.3 to 12.1. The test passes after this change.

Related issue number
Closes ray-project#42134

---------

Signed-off-by: Archit Kulkarni <[email protected]>
raulchen pushed a commit to raulchen/ray that referenced this pull request Jan 19, 2024
…ge to 12.1 (ray-project#42246)

After the Ray 2.9 release, the release test for the GPU Docker example cluster YAML file started failing with

2023-12-23 03:00:43,078 VINFO command_runner.py:371 -- Running `docker run --rm --name ray_nvidia_docker -d -it  -e LC_ALL=C.UTF-8 -e LANG=C.UTF-8 --shm-size='2301055426.56b' --runtime=nvidia --net=host rayproject/ray:latest-gpu bash`
24897079968c098daccf1ed65a0bea5d3d9e3df84de201ea20f1a34b0363975c
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: requirement error: unsatisfied condition: cuda>=11.8, please update your driver to a newer version, or use an earlier cuda container: unknown.
The likely cause is Ray 2.9 increased the required CUDA version to 11.8. This PR updates the CUDA version used in the GCP VM image in the example cluster YAML file from 11.3 to 12.1. The test passes after this change.

Related issue number
Closes ray-project#42134

---------

Signed-off-by: Archit Kulkarni <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Release test gcp_cluster_launcher_gpu_docker failed
3 participants