Attempt to pull from a custom cache of images #2009
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Docker Hub now limits the number of pulls against its repository for unauthenticated users. While we can login to Travis in job using secret variables, these are not available in forked repositories. As a result, PRs coming from forks that hit the docker pull limit will start failing. This is most notable in integration tests.
To work around this, we cache the images requested to our custom public repository that does not require authentication. This is not a good solution, but will help work around pulls in Travis for forked repositories for now. Bandwidth usage should be monitored, both from activity as well as for potential for abuse.
Test Plan
See if integration tests can pull images.