[HN Gopher] Pull Through Cache Repositories for Amazon Elastic C...
___________________________________________________________________
Pull Through Cache Repositories for Amazon Elastic Container
Registry
Author : dantiberian
Score : 23 points
Date : 2021-11-29 20:51 UTC (2 hours ago)
(HTM) web link (aws.amazon.com)
(TXT) w3m dump (aws.amazon.com)
| NathanKP wrote:
| Hey all! I work on the container services team at AWS. If you
| have any questions about this new feature, feel free to ask!
| literallyWTF wrote:
| How bad is the WLB
| NathanKP wrote:
| I assume by WLB you mean "Work/Life Balance"?
|
| Can't speak for every person at AWS, but I can say that I'm
| personally happy with my work/life balance working at Amazon.
| I work greater than 40 hours a week at times, but less than
| 40 hours a week other times. Overall it balances out between
| my needs and the needs of my broader team. I have the support
| of a great manager, who has never pushed me to do any extra
| overtime work that I didn't already want to, but has
| encouraged me and the team to take time for ourselves when we
| have been working really hard.
|
| I also think work life balance has a lot to do with how much
| you enjoy the work. I've worked remote for AWS for nearly 5
| years now, and my particular role at AWS gives me a lot of
| freedom in deciding what I do day to day, from writing blogs
| and technical content, to creating sample code, engaging with
| folks on social media, recording videos, travelling and
| giving talks at conferences, providing feedback on internal
| product specs, testing preproduction releases before they go
| live, etc. So the variety keeps me interested.
|
| Hope this insider perspective is helpful!
| mdeeks wrote:
| It doesn't appear there is support for Dockerhub yet. When will
| that be supported?
| NathanKP wrote:
| For images on Docker Hub there is a slightly different
| approach. As of today you can also find many of the top
| official Docker Hub images being mirrored to ECR Public, so
| you don't even need a pull through cache for those, you can
| pull from ECR Public directly:
|
| - ECR Public Gallery: https://gallery.ecr.aws/docker
|
| - Launch blog:
| https://aws.amazon.com/blogs/containers/docker-official-
| imag...
| m1keil wrote:
| Why is it the case?
|
| That sounds like a political decision and not a technical
| one.
|
| Looking at the gallery, the images I'm interested in seem
| to be built/uploaded by a different entity. Which is not
| great.
| X-Istence wrote:
| Unfortunately we can't just add this as a registry-mirrors
| in the docker daemon.json which means we still need to
| write all our Dockerfile's/build processes/container image
| selection to use the new ECR image URL, which is a shame.
|
| Google supports this within GCP:
| https://cloud.google.com/container-registry/docs/pulling-
| cac... which makes it easy to avoid going all the way to
| Docker Hub for images.
| adamgordonbell wrote:
| We were getting requests to pay docker a lot of money because of
| the volume of docker pulls we were doing. We used a pull-through
| cache on DO as a work around and its a been a big success.
|
| My colleague wrote up a guide to pull-through caching
| dockerhub.[1] Docker's pricing is a little bit funky, because a
| full image pull with all the layers costs the same as a request
| where you retrieve no layers at all.
|
| If this AWS feature were out a couple months ago and had support
| for dockerhub, I'm not sure we would have set this up.
|
| [1] https://earthly.dev/blog/pull-through-cache/
| db65edfc7996 wrote:
| >Running our test suite 2-3 times over the span of a couple
| hours would trigger the rate limit...
|
| Not to single you out, but not too hard to imagine why
| companies start enabling rate limiting. I oftentimes wonder the
| obscene amount of bandwidth being consumed by this developer
| automation. This page[0] indicates that PyPi serves 900
| terabytes daily.
|
| Seems obvious we need more turn-key solutions that enable
| caching for all of the popular package distributions (PyPi,
| NPM, Docker, etc). Too hard to configure and everyone will
| default to the path of least resistance (ie hammering the
| origin servers).
|
| [0] https://dustingram.com/articles/2021/04/14/powering-the-
| pyth...
___________________________________________________________________
(page generated 2021-11-29 23:00 UTC)