Skip to content
This repository was archived by the owner on Jun 4, 2024. It is now read-only.

[autoscaler] Improve documentation for spinning up a Ray cluster with a non-public Docker image #2

Open
jennakwon06 opened this issue Jan 28, 2021 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@jennakwon06
Copy link
Contributor

Hello-

Just a suggestion for including a documentation for spinning up a Ray cluster with a non-public Docker image.

You have to add below line to avoid "no basic auth credentials" error from docker pull step of ray up - this wasn't particularly clear from any existing docs under https://docs.ray.io/en/latest/cluster/cloud.html.

initialization_commands:
    - aws ecr get-login-password --region us-west-2 | docker login --username AWS --password-stdin 048211272910.dkr.ecr.us-west-2.amazonaws.com;

@jennakwon06 jennakwon06 added the enhancement New feature or request label Jan 28, 2021
@pdames pdames self-assigned this Jan 28, 2021
pdames pushed a commit that referenced this issue Jan 30, 2021
…ibly), minor fixes and preparations). (#13091)
@pdames pdames added the documentation Improvements or additions to documentation label Feb 23, 2021
@igorgad
Copy link

igorgad commented Jul 21, 2021

Thanks, I also needed to to set the IamInstanceProfile on node_config. As in here

node_config:
  IamInstanceProfile:
    Arn: arn:aws:iam::XXXXXXXXXX:instance-profile/ray-autoscaler-v1 

Zyiqin-Miranda pushed a commit that referenced this issue Jan 31, 2022
rkenmi pushed a commit that referenced this issue Mar 8, 2022
@vputz
Copy link

vputz commented Apr 4, 2024

As a minor addendum, I hadn't used my AWS cluster in a while and when I brought it up it said

Error response from daemon: pull access denied for [your ecr repo], repository does not exist or may require 'docker login': denied: Your authorization token has expired. Reauthenticate and try again.

ray down and ray up then tried to reuse the existing node, but since the initialization command above only seems to run on the first cluster initialization, I had to "terminate" the head instance and restart the cluster from scratch, and that seemed to pull just fine. I'm not sure if there's a way to have something like initialization_commands that runs every time you ray up or if there's another way to reauthenticate, but it was a (fairly minor) annoyance.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants