-
Notifications
You must be signed in to change notification settings - Fork 6.3k
[docker] Add docker images for linux/aarch64 platform #31537
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
Comments
For others searching about this issue, my error was
Thank you for your efforts. |
We've just merged the build job for arm64 docker images with a tag suffix: #31537 This means you can now use e.g. We haven't released images for Ray 2.2.0 - first release with Docker images will be Ray 2.3.0 (targeted for mid february) See here for all available arm64 images: https://hub.docker.com/r/rayproject/ray/tags?page=1&name=aarch64 And here for a roadmap RFC for our arm64 docker images: #31966 |
The nightly docker images for arm64 are available. See ray-project/ray#31537 (comment) for more details. Hence, users can run Ray in Docker containers on ARM machines (including Mac M1) and on ARM cloud instances (e.g. AWS Graviton).
The nightly docker images for arm64 are available. See ray-project/ray#31537 (comment) for more details. Hence, users can run Ray in Docker containers on ARM machines (including Mac M1) and on ARM cloud instances (e.g. AWS Graviton).
Description
#31522 added ARM64 wheel builds to CI. However, as discussed in the PR and in #28103, ideally users can use
rayproject/ray
images directly.We should thus add a docker image build step to CI that builds the linux/aarch64 docker images.
The main open question (at least for me) is how we make sure the platform-specific images are kept in sync and added to the potentially existing images from other platforms. Concretely:
rayproject/ray:commithash
forlinux/x86_64
andlinux/aarch64
should be the samerayproject/ray:nightly
forlinux/x86_64
andlinux/aarch64
to point to different commits?Use case
No response
The text was updated successfully, but these errors were encountered: