mirror of
https://github.com/vale981/ray
synced 2025-03-06 02:21:39 -05:00
e109c13b83
In https://github.com/ray-project/ray/blob/ray-1.11.0/docker/ray-ml/Dockerfile, the order of pip install commands currently matters (potentially a lot). It would be good to run one big pip install command to avoid ending up with a broken env. Co-authored-by: Kai Fricke <krfricke@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| autoscaler | ||
| base-deps | ||
| development | ||
| examples | ||
| ray | ||
| ray-deps | ||
| ray-ml | ||
| ray-worker-container | ||
| retag-lambda | ||
| fix-docker-latest.sh | ||
| README.md | ||
Overview of how the ray images are built:
Images without a "-cpu" or "-gpu" tag are built on ubuntu/focal. They are just an alias for -cpu (e.g. ray:latest is the same as ray:latest-cpu).
ubuntu/focal
└── base-deps:cpu
└── ray-deps:cpu
└── ray:cpu
└── ray-ml:cpu
nvidia/cuda
└── base-deps:gpu
└── ray-deps:gpu
└── ray:gpu
└── ray-ml:gpu