this post was submitted on 10 Jul 2023
377 points (92.9% liked)

Selfhosted

40394 readers
425 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 2 years ago
MODERATORS
 

This issue is already quite widely publicized and quite frankly "we're handling it and removing this" is a much more harmful response than I would hope to see. Especially as the admins of that instance have not yet upgraded the frontend version to apply the urgent fix.

It's not like this was a confidential bug fix, this is a zero day being actively exploited. Please be more cooperative and open regarding these issues in your own administration if you're hosting an instance. πŸ™

you are viewing a single comment's thread
view the rest of the comments
[–] MigratingtoLemmy@lemmy.world 9 points 1 year ago (1 children)

I will always espouse containers for critical workloads as they provide much better orchestration, especially during deployment. If your complaint is specifically against docker, I agree, we should be using k8s

[–] demesisx@programming.dev -5 points 1 year ago (4 children)

I disagree.

IMO, we should be using Nix and OCI.

[–] andrew@lemmy.stuart.fun 12 points 1 year ago

When someone says docker in the context of images today, they're already talking about the OCI format.

[–] Quill7513@slrpnk.net 2 points 1 year ago (1 children)

OCI uses Dockerfiles and runs Docker images as docker images are just KVM image, which is what OCI runs. Nix is absolute overkill for the orchestration of a web server workload and would be better for managing the container host (whatever you're running kubernetes or docker swarm on).

I don't really know how to put this, but nearly every single web service you encounter and interact with is built using a dockerfile just like how Lemmy is doing. If you're going to disqualify Lemmy as a viable platform based on it having a dockerfile, I got bad news

[–] towerful@programming.dev 1 points 1 year ago

I thought KVM was virtualisation, as in separate kernels.
And I thought containers shared the hosts kernel. Essentially an "overlay os".

So, a KVM could virtualise different hardware and CPU architectures.
Whereas a container can only use what the host has

[–] Kaizar@tezzo.f0rk.pl 1 points 1 year ago* (last edited 1 year ago) (2 children)

oof you sound exactly like some shit faced freshman who thinks he gained arcane knowledge, but in reality you don't know shit nor have experience. Yeah, p sure you were that dude in the back of cybersec class.

[–] MigratingtoLemmy@lemmy.world 1 points 1 year ago (1 children)

I missed his comment, what did he say?

[–] Kaizar@tezzo.f0rk.pl 1 points 1 year ago (1 children)

we should be using Nix and OCI.

You mean Nix as a base for OCO containers?

I don't see a problem, it's just that most people use Alpine when they want a lean base

[–] dannoffs@lemmy.sdf.org 1 points 1 year ago

They sound like the kind of person that brags about their vim configuration but actually uses a full IDE when no one is looking.