-
Notifications
You must be signed in to change notification settings - Fork 32
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
Migrating from Dockerhub to ECR #164
Comments
Hi @ababaian, |
Hey @kobi86, sounds great! Right now I have a tutorial written up on this, and it would be great to get feedback on this and make sure that there is enough information there to get it up and running. Once you can boot up a small cluster (say 1 node), we can go through the above steps to migrate the docker images to ECR. Pop into the Slack if you'd like, we can chat about it. |
Hey @ababaian . Is this issue still open? If yes, I am interested to pick this up. |
Hi @avinashsingh77 , this is actually non-critical these days. Most relevant issues for starting out are probably here: https://github.com/serratus-bio/serratus.io/issues Shoot me an email artem AT rRNA dot ca and I can get you an invite to the slack :) Welcome! |
Hey @ababaian , I have sent you an email from my gmail id for the slack invite. Thanks!! |
You should have gotten an invite a week ago or so, check spam |
Currently each instance is pulling an image from the
serratusbio
dockerhub repository. We can likely download this faster by pulling directly from ECR.This can be accomplished by:
Modify the
build_containers.sh
script to push to ECR if the environmental variableECR_ACCOUNT
is set in the same way thatDOCKERHUB_USER
works. Related, if the ECR repository does not exist, it should be created on that account:serratus-dl
,serratus-align
etc...For each instance, the
user_data
is defined in terraform launches the appropriate image/container. These will need to be changed to ECR, which may require a ECR read permission policy be added to the worker IAMFinally, within the
user_data
for each instance, ECR should be tried first, and if it is unavailable, dockerhub will be a fallback. This ensures if there's a permission/config error on the instance, at least something gets booted up and the instance doesn't stall out without a container which is the worst possible case.The text was updated successfully, but these errors were encountered: