Skip to content

systemd or OpenRC on your VPS?

VPS Hosting by wendy 38 replies 3.8K views
#31
Red1993 said:
Wait, you can have 5 boot volumes on always free?

5 boot volumes total, but only 2 always-free compute instances. So you can snapshot both and keep 3 more from terminated instances. I have one from an old ARM shape they retired. Check your limits in the console, some regions differ.

licensing is a suggestion
4 #32

I tried to convert an Oracle free tier to runit because I am an idiot. Broke the OCI agent, instance got reclaimed after 2 days of no heartbeat. Lost a Nextcloud I had not backed up. Lesson learned: free tier is free because they own the rules.

1 #33

Same here on the boot time question. My Hetzner CX11 boots in about 12 seconds with systemd. Is that good? Bad? I have no reference point. It is fast enough that I never cared to optimize.

#34

Jakarta here. My customers do not know what init is. They know if their online shop loads. I run CloudLinux with systemd on shared hosting, systemd on my reseller VPS. The only "switching" I do is cPanel to DirectAdmin because price.

wrap it, ship it, pray it
#35

Barcelona. I have a systemd box on OVH and an OpenRC box on an old Alpine install at work. The Alpine box is a pain every time we need to add monitoring. The systemd box just runs the vendor agent and done.

#36

Osaka. CLI over GUI always, but systemd over OpenRC because I do not want to write init scripts by hand. I use Arch on desktop and the systemd commands are the same on my VPS. Consistency matters more than purity.

#37

Has anyone used systemd-nspawn instead of Docker? I am curious if the init system choice affects container decisions too, or if that is a separate thread.

#38
Hoshino17 said:
Has anyone used systemd-nspawn instead of Docker?

Separate thread, but briefly: nspawn is fine for pet containers, terrible for anything you want to orchestrate. The init system on the host does not matter, what matters is whether your orchestrator expects cgroups v1 or v2, and systemd unified hierarchy is actually the modern default everywhere. So if anything systemd makes container life easier now.

CUDA cores are my love language
#39

Well this went about where I expected. The practical answer is "whatever came installed" and the reasons are automation, vendor support, and not wanting to be your own distro maintainer. I will file this under "debate settled by exhaustion rather than evidence" and get back to my Windows boxes where the init system is called Services.msc and nobody argues about it.

Have you tried restarting it?

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft