You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/05/15 17:56:02 UTC

[jira] [Updated] (BEAM-11150) Migrate Beam off of dockerhub

     [ https://issues.apache.org/jira/browse/BEAM-11150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-11150:
-----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Resolved)

Hello! Due to a bug in our Jira configuration, this issue had status:Resolved but resolution:Unresolved.

I am bulk editing these issues to have resolution:Fixed

If a different resolution is appropriate, please change it. To do this, click the "Resolve" button (you can do this even for closed issues) and set the Resolution field to the right value.

> Migrate Beam off of dockerhub
> -----------------------------
>
>                 Key: BEAM-11150
>                 URL: https://issues.apache.org/jira/browse/BEAM-11150
>             Project: Beam
>          Issue Type: Improvement
>          Components: build-system
>            Reporter: Andrew Pilloud
>            Priority: P2
>
> Dockerhub is ending their free-for-all policy and [imposing a 100 image pulls per 6 hour per IP rate limit effective November 1, 2020|https://www.docker.com/blog/scaling-docker-to-serve-millions-more-developers-network-egress/].
> This will make a number of common use cases (dataflow, multiple developers working from the same office) unreliable with the following error:
> {code:java}
> You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limits{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)