Selfhosted

53705 readers

720 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

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 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

103

How do you healthcheck your containers? (slrpnk.net)

submitted 1 day ago by Sunny@slrpnk.net to c/selfhosted@lemmy.world

40 comments fedilink hide all child comments

So recently been spending time configuring my selfhosted services with notifications usint ntfy. I've added ntfy to report status on containers and my system using Beszel. However, only 12 out of my 44 containers seem to have healthcheck "enabled" or built in as a feature. So im now wondering what is considered best practice for monitoring the uptime/health of my containers. I am already using uptimekuma, with the "docker container" option for each of my containers i deem necessary to monitor, i do not monitor all 44 of them 😅

So I'm left with these questions;

How do you notify yourself about the status of a container?
Is there a "quick" way to know if a container has healthcheck as a feature.
Does healthcheck feature simply depend on the developer of each app, or the person building the container?
Is it better to simply monitor the http(s) request to each service? (I believe this in my case would make Caddy a single point of failure for this kind of monitor).

Thanks for any input!

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

[–] Sunny@slrpnk.net 2 points 1 day ago (1 children)

Maybe a transition to a cluster homelab should be the goal of 2026, would be fun.

[–] noxypaws@pawb.social 2 points 1 day ago (1 children)

maybe! three raspis and k3s have served me mostly well for years, tho with usb/sata adapters cuz the microsd was getting rather unreliable after awhile

[–] Sunny@slrpnk.net 1 points 1 day ago (1 children)

Nice one that, fortunately i just rebuilt my server with an i5-12400 new fancy case amd slowly transitioning to an all in ssd build! I would probably lean towards a singlenode cluster using Talos.

[–] noxypaws@pawb.social 1 points 17 hours ago (1 children)

I haven't heard of Talos before, sounds like it's not fully open source?

[–] Sunny@slrpnk.net 2 points 13 hours ago* (last edited 13 hours ago)

Talos is really awesome, its a minimal OS strictly built to run kubernetes. We use it at work and its running in production for a lot of people. Its extremely minimal and can only be used via its own api, talosctl command. Its minimalism makes it great for security and less resource heavy than alternatives.

Check this out for a quick' funny taste of why one should consider using Talos >>

[60sec video from Sidero Labs, creators of Talos] https://www.youtube.com/watch?v=UiJYaU16rYU

Talos is under MPL 2.0, afaik that is open-source.