this post was submitted on 10 Nov 2024
40 points (91.7% liked)

Selfhosted

60664 readers
479 users here now

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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
40
How to maintain a local repository of docker images in case they go offline? (lemmy.world)
submitted 2 years ago* (last edited 2 years ago) by ComradeMiao@lemmy.world to c/selfhosted@lemmy.world
19 comments fedilink hide all child comments
 

Thanks for all the great replies!

you are viewing a single comment's thread
view the rest of the comments
[–] just_another_person@lemmy.world 28 points 2 years ago (2 children)

Retag and push to a local registry. Lots of options out there for setting one up.

Honestly, you already have the image locally if you've pulled it. You don't really need to run a registry unless you're dead set on it. You can also flatten and export containers for backup if you really want.

[–] thirdBreakfast@lemmy.world 16 points 2 years ago (1 children)

Two good points here OP. Type docker image ls to see all the images you currently have locally - you'll possibly be surprised how many. All the ones tagged <none> are old versions.

If you're already using github, it includes an package repository you could push retagged images to, or for more self-hosty, a local instance of Forgejo would be a good option.

[–] foster@lemmy.fosterhangdaan.com 9 points 2 years ago

I'd also like to add that you can save an image to a local file using docker image save and load them back using docker image load. So, along with the options mentioned above, you have plenty of options to backup images for offline use.

[–] rikudou@lemmings.world 6 points 2 years ago (2 children)

Honestly, you already have the image locally if you've pulled it.

I guess not everyone treats their PC as an ephemeral storage, huh? I don't trust anything that's available only locally to survive.

[–] just_another_person@lemmy.world 6 points 2 years ago

Well the question is about a container disappearing from a public registry, in which case nothing would happen if it's already pulled locally. Figuring where to go from there is the other half of that problem.

[–] GBU_28@lemm.ee 1 points 2 years ago

Then backup whatever you set your docker local storage to?