This is awesome work, I'm happy to see systemd on musl getting more attention. Poor Khem was doing it all by himself for years.
this post was submitted on 05 Sep 2024
115 points (98.3% liked)
Linux
47970 readers
1291 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Very very nice work. Thanks for your effort and willingness to experiment with new stuff. i would definitely be interested in trying it out once it reaches "production".
While I do appreciate the effort, I cannot understand, who in their right mind would use musl and systemd together. For what purpose? If a person was already willing to manage a musl system, why wouldn't he also prefer sysVinit or runit or whatever?
I want to try alpine out but the lack of systemd support is a blocker since I don't want to add openrc support to all my Ansible playbooks that rely on systemd services and timers
It seems like postmarketOS is porting systemd to alpine for their next stable version, just something to keep an eye on
Maybe because that person uses systemd everywhere else and just doesn't want the overhead of maintaining two different init systems.
He already has the overhead of maintaining to C libraries, which is a lot bigger problem.
Well then the answer will most likely be: because they can and want to do it.
The reasons for choosing Musl over glibc are largely unrelated for choosing a service manager. You can want one without the other just fine.
My understanding is that it boots faster. That's a nice thing to have on a container that spins up on demand.
It boots faster than openRC (which is painfully slow). But runit is a lot faster than systemd, and there are init systems even faster than runit. And they all already work with musl. There is even dinit system specifically designed for containers.
What is the name of the dinit system designed for containers?
"dinit"
In general (there are exceptions) containers do not use service managers at all. They start 1 command and that's it.
My understanding is that it boots faster.
I tested this with EL6 and EL7. There was no discernible difference. It was all theories and brochureware.
I would say "finally", but I've given up already.
I don't see systems booting with systemd in any near future of any dimension. Instead I now run "terribly slow" OpenRC on my systems. Poor me.
Instead I now run “terribly slow” OpenRC on my systems.
I suspect you're entirely free of init problems where you raise your fists to the heavens and ask WHAT ARE YOU DOING as if it'll tell you why systemd is on holiday now.
What is the aim of this project? Is there a reason why we want to port systemd to distributions which do not want to use glibc?
For all the cases where musk might have advantages.
I like that musl helps build smaller containers. And sometimes I need systemd in a container.
Systemd bloats the container a lot more than glibc.
If I need systemd for a specific use, like testing systemd services, that’s essential, not bloat.
If I need systemd for a specific use, like testing systemd services
So you're hoping to test systemd in this theoretical test environment, but your prod isn't built like this? Tell us why you're ignoring the first rule of testing and deploying internal software?
The same containers can be used for dev, test and production.
I wouldn't recomend testing any software for glibc system on a musl system.
Libc has more overhead and attack surface