this post was submitted on 03 Jul 2024
30 points (94.1% liked)

Selfhosted

39964 readers
381 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 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!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
30
Is it safe to automatically pull and update docker containers? (lemmy.kde.social)
submitted 4 months ago* (last edited 4 months ago) by tubbadu@lemmy.kde.social to c/selfhosted@lemmy.world
25 comments fedilink hide all child comments
 

Hello! I was wondering if running periodically a script to automatically pull new images for all my containers is a good or a bad idea. I'd run it everyday at 5.00AM to avoid interruptions. Any tips?

EDIT: Thanks to everyone for the help! I'll install Watchtower to manage the updates

you are viewing a single comment's thread
view the rest of the comments
[–] DARbarian@kbin.run 17 points 4 months ago (2 children)

Why not just let Watchtower do it for you?

[–] tubbadu@lemmy.kde.social 14 points 4 months ago (1 children)

Because I was today years old when I found out this beautiful piece of software exist :D

thank you very much!

[–] paris@lemmy.blahaj.zone 2 points 4 months ago

I use Watchtower and haven't had any major issues in the two(?) years I've been using it. Make sure you use persistent volumes for your containers and make sure you back up those volumes. If anything breaks, you can roll back to before the update.

If you don't use persistent volumes, you'll lose data when Watchtower takes down the image and replaces it with the newer one (which doesn't copy over ephemeral volumes).

I also recommend for database containers to use an image tag that won't update with breaking changes. Don't use postgres:latest, use postgres:15.2 or something like that (whatever the image you're using the database for recommends).

[–] haui_lemmy@lemmy.giftedmc.com 3 points 4 months ago

Pretty solid advice.

One could argue though that a backup script could pull the particular container image right after doing the backup to have maximum coverage.

If someone is already that adept at scripting to rely on a script to do automatic backups, they can very well pull the new images and clean old ones.

I‘m one of those who have a backup script and still use watchtower.