Selfhosted

39488 readers

306 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.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Why docker (feddit.it)

submitted 8 months ago by Shimitar@feddit.it to c/selfhosted@lemmy.world

81 comments fedilink hide all child comments

Hi! Question in the title.

I get that its super easy to setup. But its really worthwhile to have something that:

runs everything as root (not many well built images with proper useranagement it seems)
you cannot really know which stuff is in the images: you must trust who built it
lots of mess in the system (mounts, fake networks, rules...)

I always host on bare metal when I can, but sometimes (immich, I look at you!) Seems almost impossible.

I get docker in a work environment, but on self hosted? Is it really worth while? I would like to hear your opinions fellow hosters.

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

[–] scrubbles@poptalk.scrubbles.tech 3 points 8 months ago

This is a really bad take. I'm all for OSS, but that doesn't mean that there isn't value with things like Docker.

Yes, developers know less about infra. I'd argue that can be a good thing. I don't need my devs to understand VLANs, the nuances of DNS, or any of that. I need them to code, and code well. That's why we have devops/infra people. If my devs to know it? Awesome, but docker and containerization allows them to focus on code and let my ops teams figure out how they want to put it in production.

As for OSS - sure, someone can come along and make an OSS solution. Until then - I don't really care. Same thing with cloud providers. It's all well and good to have opinions about OSS, but when it comes to companies being able to push code quickly and scalably, then yeah I'm hiring the ops team who knows kubernetes and containerization vs someone who's going to spend weeks trying to spin up bare iron machines.