this post was submitted on 30 Jan 2026
67 points (97.2% liked)

Selfhosted

60093 readers
719 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:

  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.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

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

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 30 days old, your post is exempt from this rule as long as you continue to engage in comments.

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
67
Do you backup your docker images? (lemmy.world)
submitted 4 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
[–] ada@lemmy.blahaj.zone 51 points 4 months ago (2 children)

Nope. Data directories and compose files only.

[–] Onomatopoeia@lemmy.cafe 4 points 4 months ago (3 children)

Curious, have you tested rebuilding using this approach?

It makes sense to me, if the compose files are up-to-date, it should just work.

I'd only be concerned about ensuring I capture changes made to the container that happened after initial build.

[–] surewhynotlem@lemmy.world 10 points 4 months ago

That's the secret. I never change the container.

If you absolutely must do some config on the container, then have a container creation script that creates a new container with the right settings and use that.

#pipelines

[–] teawrecks@sopuli.xyz 4 points 4 months ago

I feel like if that's something you're doing, you're using containers wrong. At least docker ones. I expect a container to have no state from run to run except what is written to mounted volumes. I should always be able to blow away my containers and images, and rebuild them from scratch. Afaik docker compose always implicitly runs with --rm for this reason.

[–] enchantedgoldapple@sopuli.xyz 4 points 4 months ago

I can attest to it. Lately my server needed to be repaired and got its entire disk wiped. Fortunately I managed to back up my compose files and bind mounts. After reinstalling the OS and transferring the backed up contents, I ran 'docker compose up' and eventually everything came back up exactly how they were when being backed up. Even the Postgres backup of Joplin was recovered purely from its bind mount.

[–] Bakkoda@lemmy.world 3 points 4 months ago

This is how i do it. I can delete everything, repull and redeploy like nothing ever happened.

I have one exception and thats my calibre-web container. I have all my books backed up separately and I'll be nuking that whole set up eventually.