Selfhosted
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.
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!
view the rest of the comments
I’ll consider it a drop-in replacement when Kubernetes can use it.
Not sure what you mean, Podman isn’t a container runtime and Kubernetes has deprecated it’s docker shim anyway.
Its* docker shim
lol you’re not wrong but was it worth saying?
Yes. Very much. I understand I'm being pedantic, but I don't really do it to bash on the writer. I do it for me. It's like an itch. I see "its" being wrongly used, and writing it the correct way is like scratching that itch.
Does it make a difference? Who knows. Some people tell me to go eat dicks, some people thank me because they either didn't know the difference, or it was a typo (ironically, I've made this very mistake in the past!)
Also, I understand that languages evolve, so who knows and "it's" instead of "its" becomes the norm. But at the moment, I find it bothersome (like "your/you're" and "would of")
And I also understand that we all come from a variety of backgrounds and educational skills. Some people know less stuff than I do, some people know waaaay more than I do. I personally appreciate when someone corrects me.
In the end, this is just lemmy, so I don't take things too seriously here (in spite of this lengthy essay, lol!) This is an escape for me. If you got this far, thanks for reading.
Kubernetes uses cri-o nowadays. If you're using kubernetes with the intent of exposing your docker sockets to your workloads, that's just asking for all sorts of fun, hard to debug trouble. It's best to not tie yourself to your k8s clusters underlying implementation, you just get a lot more portability since most cloud providers won't even let you do that if you're managed.
If you want something more akin to how kubernetes does it, there's always nerdctl on top of the containerd interface. However nerdctl isn't really intended to be used as anything other than a debug tool for the containerd maintainers.
Not to mention podman can just launch kubernetes workloads locally a.la. docker compose now.