this post was submitted on 01 Jun 2023
3 points (100.0% liked)

Technology

37716 readers
509 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

Everyone (and their mother) have been trying to convince me that I should use one of my less loaded servers to be a Fediverse node. However, all Fediverse software packages I checked only support being installed on complicated systemd + Docker machines. My servers don't have either of those, because neither systemd nor Docker even exist on OpenBSD and illumos.

I know that it would be possible to manually install (e.g.) Lemmy, assuming that I won't ever need official support, but I wonder why the world outside a limited subset of the Linux ecosystem is - at most - an afterthought for Fediverse developers.

How can I help to change that?

you are viewing a single comment's thread
view the rest of the comments
[–] dan@upvote.au 1 points 1 year ago (1 children)

It's "annoyingly hard" because you're not using modern tooling. If Docker is unavailable on your preferred OS, then that OS is stuck in the past. Simple as that.

Docker makes it easy to install a program, including all its dependencies, in a repeatable way. Since you're familiar with BSD, it's similar to jails except with better isolation, fewer security holes/issues, and the software you want to run is preinstalled. Docker containers are essentially mmutable which makes upgrades easy - just throw away the old container and replace it with the new version. (persistent files are stored separately, in "volumes")

You can of course manually install the same software by looking at the Dockerfile and manually performing the same steps, but there's no guarantee that it'd work well on an unsupported OS.

[–] tux0r@feddit.de 1 points 1 year ago (1 children)

It’s “annoyingly hard” because you’re not using modern tooling.

Calling Docker "modern" is a stretch, as it's not much more than glorified Solaris Zones, but please enlighten me: Which feature of a federated web application requires modern tooling?

Since you’re familiar with BSD, it’s similar to jails

OpenBSD does not have jails.

except with better isolation

How so?

fewer security holes/issues

Actually, not using Docker prevents a number of security holes/issues.

and the software you want to run is preinstalled.

If you grab an image with it. You could as well just grab a tar archive with it... with less side effects.

Docker containers are essentially mmutable which makes upgrades easy

And security patches impossible.

[–] dan@upvote.au 1 points 1 year ago

Calling Docker “modern” is a stretch, as it’s not much more than glorified Solaris Zone

And yet the OS you're using doesn't support it. Hmm.

OpenBSD does not have jails.

Sorry, I didn't realise that these are FreeBSD-specific (I guess? I'm not too familiar with BSD)

Which feature of a federated web application requires modern tooling?

Deployment. All web apps and APIs are moving towards containerization - Docker for smaller scale deployments, and Kubernetes for large-scale deployments.

except with better isolation How so?

I didn't think jails had CPU, memory, or process limits similar to what cgroup2 provides, but it looks like this functionality was added to FreeBSD at some point. Sorry for the incorrect information.

Actually, not using Docker prevents a number of security holes/issues.

Sure, Docker has had a few issues, but overall it's more secure to run your apps in Docker containers. If an app gets compromised, the attacker will generally be stuck inside the Docker container rather than getting access to your entire system. If you're worried about (very rare) container escape security holes, using unprivileged containers helps - You can run the app inside the container as an unprivileged user, and you can also run the entire Docker container as an unprivileged user on the host system.

And security patches impossible.

Security patches are easier than if you used a tar archive to install the software. With a tar archive you threw into /opt or whatever, the app and its config/data are often stored together, so you need to be mindful of things like not overriding customized config files. Since Dockers containers are immutable and all the actual data is stored elsewhere, it's always safe to delete the container and replace it with a patched version.