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
As a Galasa developer, I want to use GHCR as a Docker cache, so that we don't encounter the Dockerhub pull limit during our build pipelines.
Background
We currently have a Docker proxy cache set up in Harbor and many of our custom images pull FROM a Docker official image like alpine. The proxy cache allows us not to hit the Dockerhub pull limit (100 pulls every 6 hours).
We need to set up the same thing for the GHCR so that when we eventually get rid of Harbor, our Docker builds don't start failing, and instead pull from the GHCR proxy cache.
So all FROM statements in our Dockerfiles that are like: FROM harbor.galasa.dev/docker_proxy_cache/library/alpine:3.18.4 would become FROM ghcr.io/library/alpine:3.18.4.
Tasks
Set up the Docker proxy cache for GHCR
Update all FROM statements in Dockerfiles to use this new proxy cache
Delete cached images from Harbor / delete Harbor if ready to do so at this stage
The text was updated successfully, but these errors were encountered:
Story
As a Galasa developer, I want to use GHCR as a Docker cache, so that we don't encounter the Dockerhub pull limit during our build pipelines.
Background
We currently have a Docker proxy cache set up in Harbor and many of our custom images pull
FROM
a Docker official image like alpine. The proxy cache allows us not to hit the Dockerhub pull limit (100 pulls every 6 hours).We need to set up the same thing for the GHCR so that when we eventually get rid of Harbor, our Docker builds don't start failing, and instead pull from the GHCR proxy cache.
So all
FROM
statements in our Dockerfiles that are like:FROM harbor.galasa.dev/docker_proxy_cache/library/alpine:3.18.4
would becomeFROM ghcr.io/library/alpine:3.18.4
.Tasks
FROM
statements in Dockerfiles to use this new proxy cacheThe text was updated successfully, but these errors were encountered: