• 0 Posts
  • 5 Comments
Joined 2 months ago
cake
Cake day: December 4th, 2025

help-circle


  • gerowen@piefed.socialtoSelfhosted@lemmy.worldDocker security
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    Systemd has all sorts of options. If a service has certain sandbox settings applied such as private /tmp, private /proc, restricting access to certain folders or devices, restricting available system calls or whatever, then systemd creates a chroot in /proc/PID for that process with all your settings applied and the process runs inside that chroot.

    I’ve found it a little easier than managing a full blown container or VM, at least for the things I host for myself.

    If a piece of software provides its own service file that isn’t as restricted as you’d like, you can use systemctl edit to add additional options of your choosing to a “drop-in” file that gets loaded and applied at runtime so you don’t have to worry about a package update overwriting any changes you make.

    And you can even get ideas for settings to apply to a service to increase security with:

    systemd-analyze security SERVICENAME



  • I literally have clothes hanging on a line across the living room because our just out of warranty $1,000+ Samsung “smart dryer” died again a month after I replaced every sensor and the heating element, and I just don’t feel like taking it apart again to “maybe” find the problem.

    Before this we just had a plain white box from Maytag; easy to work on, cheap replacement parts. It was probably 30 years old when the motor seized and my wife asked for newer, fancier machines. Big mistake.