-
Notifications
You must be signed in to change notification settings - Fork 3
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
era5 CodeBuild pipeline failed due to dockerhub pull rate limit on miniconda #4
Comments
Tipped off by @zflamig , I see in this AWS Announcement it says: "Within weeks, AWS will deliver a new public container registry that will allow developers to share and deploy container images publicly. This new registry will allow developers to store, manage, share, and deploy container images for anyone to discover and download. Developers will be able to use AWS to host both their private and public container images, eliminating the need to use different public websites and registries. Public images will be geo-replicated for reliable availability around the world and offer fast downloads to quickly serve up images on-demand. Anyone (with or without an AWS account) will be able to browse and pull containerized software for use in their own applications. " |
I don't know about miniconda but miniforge is on quay.io to avoid that. |
@zflamig, you switched to miniforge3 somewhere, right? Where is that code? |
https://github.com/zflamig/dask-worker/blob/master/Dockerfile#L1 here we are using the miniforge3 now |
Thanks for all this hard work gentlemen, you have saved me a ton of time getting some basic testing done. |
@rsignell-usgs - this is where I got to, for if you have any ideas https://github.com/RichardScottOZ/dask-era5/blob/main/notebook/pangeoFargateTrialSA.ipynb |
@zflamig , the CodeBuild pipeline failed due to dockerhub pull rate limit on miniconda
@ocefpaf, do you know if there is a different place to pull the Miniconda Container from now?
The text was updated successfully, but these errors were encountered: