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

[docker][rfc] Roadmap for Docker images from Ray 2.3 onwards #31966

Closed
krfricke opened this issue Jan 26, 2023 · 3 comments
Closed

[docker][rfc] Roadmap for Docker images from Ray 2.3 onwards #31966

krfricke opened this issue Jan 26, 2023 · 3 comments
Assignees
Labels
stale The issue is stale. It will be closed within 7 days unless there are further conversation

Comments

@krfricke
Copy link
Contributor

We are currently adding support for arm64 Docker images here: #31861

This issue tracks the planned roadmap and open discussion points for the Ray Docker images and can be used for discussions.

Ray 2.3

Ray 2.3 will be the first release for which we release arm64-compatible Docker images.

These images will be built for

  • CPU
  • CUDA 11.2
  • CUDA 11.3
  • CUDA 11.6

The image tags will have a -aarch64 suffix and thus need to be specified explicitly.

We will not publish 2.3.0 as :latest-aarch64 - instead :2.3.0-aarch64 has to be used explicitly. The reason for this is that we may remove suffixes completely in the next release, and then we would have a stale :latest-aarch64 image pointing to an older release.

We will not build ray-ml images for aarch64. This is mostly due to lack of compatibility of some dependencies with arm64.

Ray 2.4

For Ray 2.4, we aim to provide multiplatform images. This means that the suffixes will not be needed anymore: Docker will automatically choose the correct image given the regular tag.

This also means that we will likely stop publishing -aarch64 tags to docker hub (hence why we don't publish :latest-aarch64 in 2.3.0)

@stale
Copy link

stale bot commented Jun 10, 2023

Hi, I'm a bot from the Ray team :)

To help human contributors to focus on more relevant issues, I will automatically add the stale label to issues that have had no activity for more than 4 months.

If there is no further activity in the 14 days, the issue will be closed!

  • If you'd like to keep the issue open, just leave any comment, and the stale label will be removed!
  • If you'd like to get more attention to the issue, please tag one of Ray's contributors.

You can always ask for help on our discussion forum or Ray's public slack channel.

@stale stale bot added the stale The issue is stale. It will be closed within 7 days unless there are further conversation label Jun 10, 2023
@stale
Copy link

stale bot commented Aug 12, 2023

Hi again! The issue will be closed because there has been no more activity in the 14 days since the last message.

Please feel free to reopen or open a new issue if you'd still like it to be addressed.

Again, you can always ask for help on our discussion forum or Ray's public slack channel.

Thanks again for opening the issue!

@stale stale bot closed this as completed Aug 12, 2023
@pingsutw
Copy link
Contributor

@krfricke any update on this? I didn't see multiplatform images on dockerhub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale The issue is stale. It will be closed within 7 days unless there are further conversation
Projects
None yet
Development

No branches or pull requests

2 participants