5 ms·

Questions for Silverblue / Atomic Users: I tried Silverblue a couple years ago and found myself rpm-ostree layering some basic tools like Fish shell and Mosh.

Questions for Silverblue / Atomic Users: I tried Silverblue a couple years ago and found myself rpm-ostree layering some basic tools like Fish shell and Mosh. Is layering still the preferred method for installing these types of tools or do you have "generic" container (made with toolbox/distrobox) that you jump into for generic shell work in like ssh'ing around and file management? Also, how do you handle things like custom services? For example, Nebula overlay network doesn't really have an installer. Its just a single binary. I manually put that in /usr/local/bin, put the configs in /etc/nebula, chmod those configs to hide them, update selinux, and create a service file for it. How would I do that in an immutable system?

jcastro 3y ago
`/usr/local` is writeable so no change there, that should work fine. I keep a container as my "day to day" linux and just have my terminal autolaunch into mine. You can use any distro's container for this so it's personal preference. I'm using Prompt, it's a new terminal designed to make the toolbox/distrobox flow much nicer: https://gitlab.gnome.org/chergert/prompt https://gitlab.gnome.org/chergert/prompt It's still relatively new so it isn't on flathub yet but it makes everything mostly seamless.
- discardedrefuse 3y ago
  Good to know. Thanks for the info! I'll be keeping on eye on Prompt.
- curt15 3y ago
  How do you deal with the lack of systemd in the container? Where do you put software that ship systemd unit files?
  - jcastro 3y ago
    I use containerized versions of things, ubuntu and chainguard images mostly. You can always create containers with init if that's how you want to do that though. Some distros publish images that come that way: https://github.com/89luca89/distrobox/blob/main/docs/useful_tips.md#using-init-system-inside-a-distrobox https://github.com/89luca89/distrobox/blob/main/docs/useful_...
    - curt15 3y ago
      Thanks, that link is chockful of useful tips!

jcastro 3y ago

`/usr/local` is writeable so no change there, that should work fine. I keep a container as my "day to day" linux and just have my terminal autolaunch into mine. You can use any distro's container for this so it's personal preference. I'm using Prompt, it's a new terminal designed to make the toolbox/distrobox flow much nicer: https://gitlab.gnome.org/chergert/prompt https://gitlab.gnome.org/chergert/prompt It's still relatively new so it isn't on flathub yet but it makes everything mostly seamless.

discardedrefuse 3y ago
Good to know. Thanks for the info! I'll be keeping on eye on Prompt.
curt15 3y ago
How do you deal with the lack of systemd in the container? Where do you put software that ship systemd unit files?
- jcastro 3y ago
  I use containerized versions of things, ubuntu and chainguard images mostly. You can always create containers with init if that's how you want to do that though. Some distros publish images that come that way: https://github.com/89luca89/distrobox/blob/main/docs/useful_tips.md#using-init-system-inside-a-distrobox https://github.com/89luca89/distrobox/blob/main/docs/useful_...
  - curt15 3y ago
    Thanks, that link is chockful of useful tips!