Selfhosted

61416 readers

557 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

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
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.
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:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Do you backup your docker images? (lemmy.world)

submitted 6 months ago by thelocalhostinger@lemmy.world to c/selfhosted@lemmy.world

36 comments fedilink hide all child comments

Not containers and data, but the images. The point would be reproducability in case a remote registry does not contain a certain image anymore. Do you do that and how?

you are viewing a single comment's thread
view the rest of the comments

[–] realitaetsverlust@piefed.zip 1 points 6 months ago (1 children)

I'm kinda confused by all of the people here doing that tbh.

The entire point of dockerfiles is to have them produce the same image over and over again. Meaning, I can take the dockerfile, spin it up on any machine on gods green earth and have it run there in the exact same state as anywhere else, minus eventual configs or files that need to be mounted.

Now, if I'm worried about an image disappearing from a remote registry, I just download the dockerfile and have it stored locally somewhere. But backuping the entire image seems seriously weird to me and kinda goes against of the spirit of docker.

[–] crater2150@feddit.org 2 points 6 months ago (1 children)

A lot of Dockerfiles start with installing dependencies via the base image's package manager, without specifying exact versions (which isn't always possible, as most distros don't keep all history of all packages in their repos). So all your dependencies may have different versions, when you build again.

[–] realitaetsverlust@piefed.zip 1 points 6 months ago

True, but I got two problems with that thought chain:

I don't want any outdated dependencies within my network. There might be a critical bug in them and if I back up the images, I keep those bugs with me. That seems pretty silly.
If an application breaks because you updated dependencies, you either have to upgrade the application aswell or got some abandonware on your hands, in which case it's probably time to find a new one.