Selfhosted

60970 readers

649 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

111

How do you keep docker/podman containers up-to-date? (lemmy.world)

submitted 3 years ago by cat@lemmy.world to c/selfhosted@lemmy.world

66 comments fedilink hide all child comments

I used to simply use the 'latest' version tag, but that occasionally caused problems with breaking changes in major updates.

I'm currently using podman-compose and I manually update the release tags periodically, but the number of containers keeps increasing, so I'm not very happy with this solution. I do have a simple script which queries the Docker Hub API for tags, which makes it slightly easier to find out whether there are updates.

I imagine a solution with a nice UI for seeing if updates are available and possibly applying them to the relevant compose files. Does anything like this exist or is there a better solution?

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

[–] deafboy@lemmy.world 2 points 3 years ago (2 children)

You obviously know a thing or two about Kubernetes. I'm trying to learn. I've been at the cloud native conference, I attended the vmware tanzu course, even played with microk8s on my laptop. I still look for the "aha!" moment, when I understand the point of it all, and everything clicks into place.

However, whenever I see somebody describe their setup, I just cringe. It all just feels like we're doing simple things in an obscure and difficult way.

The technology has been here for almost a decade, and it's obviously not going away. How can I escape the misery, and start loving k8s?

Picture somehow related...

[–] Millwiller@lemm.ee 2 points 3 years ago

For sure, just stacking turtles all the way down... 🐢 It's definitely overkill for a home lab, but I'm an infra engineer, and it's what I use daily, so setting it up was worth it because I'm already really familiar with the stack. That said, I do absolutely love having declarative setup at home because I'll sometimes go months without touching things. Before I spent the time to make it declarative, I'd frequently forget how I set certain things up and waste time redoing, or figuring out where I left off. Now I just check commit history and I'm always moving forward.