Hacker News Reader

Comment by silisili | Hacker News Reader

Interesting. Anyone familiar with it? I'm curious if it's container per application, or container per distro supported. Having never run a system like this, how do you manage files? If I have samba from Debian and nginx from Arch, how does one edit their respective configs and such?

View on HN

Not vanillaos, but bluefin/silverblue. You can manage many user level programs via toolbox or distrobox in a similiar way as a regular distro, but the packages are installed in your $HOME. You can still use regular containers as well too. Although you can still add extra system level stuff if you desire via layering (or soon via systemd sysext)

This is what I do. Works amazingly well.

Ive read the source code of apx (the package manager) and its basically just a distrobox wrapper. From what I understand, It creates a container for each distribution and packages are installed in that container.

Filesystem is automatically mounted to the container. I believe this one use LXC through distrobox, Fedora silverblue does the same with toolbox which used podman.

If you want to give it a try you can install distrobox or toolbox right now on any distro, this is not unique to immutable readonly distros. This allows you to separate system / userland package management and have access to say, pacman on a fedora for example.

Not much familiar with it, but familiar with the concept: it's a fail.

If you want a comfy modern system goes for NixOS/Guix System on top of zfs. Safety came from design, not from isolation. Comfort came from autonomous power not quickly import third parties blob and so on. Such distros are like btrfs vs zfs. A tentative to denied the fact a model needed by some actors is total crap.

It's distrobox, so an LXC container per app.

User filesystem is totally transparent.

Reply on news.ycombinator.com