[QGIS-Developer] Docker pull rate limit / Travis

[Richard Duivenvoorde]

Yes, I hit that too. thanks for bringing this up!

Another idea: as the docker is actually more or less 'static' (??? or is is pushed to hub on every build ???), can we (or Travis) not 'cache' it? As in" place it somewhere so it can be 'created/started' fresh any time, but not 'fetched' upon every build? 
Or does this loose the whole purpose of this...
Caching could be: put the image on some webserver of somebody with 'unlimited' bandwidth (like some universities, providers or (unix)usergroups?).

BUT: As QGIS is getting bigger and bigger, we have to find solutions for this kind of 'size'-issues when using 'free' services. Same with for example the use of OSM-tiles or Nominatim-service, Transifex etc etc... We have to be either creative/clever, OR setup our own stuff...

Regards,

Richard Duivenvoorde


On 1/4/21 9:57 AM, pathmapper wrote:
> Hi,
> 
> due to the recently introduced docker pull rate limits there are currently quite a lot Travis builds failing because of such a limit.
> 
> According to this blogpost: https://www.docker.com/blog/what-you-need-to-know-about-upcoming-docker-hub-rate-limiting/
> 
> "[...] non-commercial open source projects can apply for a sponsored Open Source Docker account by filling out this application. No pull rate restrictions will be applied to namespaces approved as non-commercial Open Source projects."
> 
> Don't know if such an application for a sponsored Open Source Docker account would be something the QGIS project would be interested in or if the QGIS Docker account is already sponsored. A sponsored Docker account might help a little bit reaching these limits e.g. regarding pulling:
> 
> https://hub.docker.com/r/qgis/qgis3-build-deps