You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recent Appveyor runs have failed due to dockerhub's rate limiting (see e.g., #227).
We had this in the early days of the datalad-dataverse extension, too, and a fix we temporarily employed was a Github action performing a DockerHub login (see datalad/datalad-dataverse@f6e8cfd)
I'm not sure if this is the right way to go about this, though. The past exploration was here: datalad/datalad-dataverse#47
The text was updated successfully, but these errors were encountered:
#199 is also a promising directory. If implemented, we would only pull each unique layer once for each CI run.
Better yet, we could preload the docker instance with all relevant images from an appveyor cache. Even for the actual image building, docker might be clever enough to reuse local image layers.
Caching and preloading is already done in the datalad-ria CI setup, and could be copied.
Recent Appveyor runs have failed due to dockerhub's rate limiting (see e.g., #227).
We had this in the early days of the datalad-dataverse extension, too, and a fix we temporarily employed was a Github action performing a DockerHub login (see datalad/datalad-dataverse@f6e8cfd)
I'm not sure if this is the right way to go about this, though. The past exploration was here: datalad/datalad-dataverse#47
The text was updated successfully, but these errors were encountered: