38

How to maintain a local repository of docker images in case they go offline?

posted
*
by
Avatar
ComradeMiao@lemmy.world
in
Avatar
selfhosted@lemmy.world
17 comments
hidereport

Thanks for all the great replies!

Sort:
HotTopControversialNewOld
Avatar
DasFaultier@sh.itjust.works
3 points

At my job, we run goharbor.io and use its Replications feature to do just that.

permalink
report
reply
Avatar
Scrubbles@poptalk.scrubbles.tech
3 points
*

For most of you suggesting hosting a repository - yes but,

Host forgejo. Just host the git mirror. It comes with a package repo out of the box. Then you have the source code and the docker images

permalink
report
reply
Avatar
rearview@lemmy.zip
2 points

An alternative method is to run an actions workflow that syncs from upstream images directly, like what Forgejo actually do.

https://code.forgejo.org/forgejo/oci-mirror

permalink
report
parent
reply
Avatar
Scrubbles@poptalk.scrubbles.tech
2 points

oh freaking awesome, this looks amazing! Thank you so much for this!

permalink
report
parent
reply
Avatar
Matt@lemmy.ml
1 point

Host forgejo.

Or Gitea if you want to run the upstream.

permalink
report
parent
reply
Avatar
undefined@lemmy.hogru.ch
0 points

Isn’t a Docker registry just HTTP? Would a caching proxy be too hard to use for this?

permalink
report
reply
Avatar
timbuck2themoon@sh.itjust.works
4 points

Just use a sonatype nexus 3 image and proxy docker hub, etc. Then you pull images through it.

permalink
report
reply
Avatar
precarious_primes@lemmy.ml
3 points

We run this at work so we have forever copies of image tags and to reduce dockerhub rate limit issues. Works well even for a large dev team.

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 5.2K

    Monthly active users

  • 1.8K

    Posts

  • 19K

    Comments

Community moderators