Eleven init systems enter, one init system leaves.
  • Quik@infosec.pubEnglish
    75·
    3 天前

    One thing the author probably hasn’t done yet or just doesn’t mention is that you can configure .container services with systemd-podman units (often called quadlets), e.g. a simple MariaDB container would look like this:

    [Unit]
Description=MariaDB container

[Container]
Image=docker.io/mariadb:latest
Environment=MYSQL_ROOT_PASSWORD=rootpassword
Environment=MYSQL_USER=testuser
Environment=MYSQL_PASSWORD=testpassword
Environment=MYSQL_DATABASE=testdb

[Install]
WantedBy=multi-user.target

    Short intro Full reference

    This is superb, because it means your containers finally feel well-integrated with the rest of the OS and you can use systemctl, journalctl, etc. just like you would with other services.

    Personally, I use this as an alternative to Podman/Docker compose and have been very happy with it running rootless containers from Nextcloud, Pufferpanel, Forgejo, Authentik, etc. (ask me for .container files if you need any help, I’m currently working on a small repo with a collection)

      • Quik@infosec.pubEnglish
        2·
        3 天前

        Yeah, it’s great that Gitea/Forgejo has a copy-paste snippet in the docs, but you can actually use that with pretty much every container.

        There is this useful tool to convert containers, podman commands or even compose files to podman-systemd units: https://github.com/containers/podlet

      • Quik@infosec.pubEnglish
        3·
        3 天前

        Your distrust is kind of reasonable: I’ve been using this a lot for the past year and there definitely were two or three moments where it was a bit annoying, too little transparent on what commands will be run, etc.

    • dwt@feddit.orgDeutsch
      11·
      3 天前

      I like this, but even though pod man runs perfect rootless, quadlets can only run as root for now :-(

        • dwt@feddit.orgDeutsch
          1·
          2 天前

          How do you do that? Please link a description. This has been a major stumbling block for me

            • dwt@feddit.orgDeutsch
              1·
              2 天前

              Yeah, that works, but it means the services cannot be managed by systemctl as root anymore. Or am I missing something?

              • mholiv@lemmy.world
                2·
                2 天前

                You can if you want to. But I don’t think that is best practice. The idea of quadlets is the bring Linux norms to containers. You contain and manage all permissions for that container in that user.

                I personally have completely separated users and selinux mls contexts for each container group (formerly docker compose file) and I manage them thusly. It’s more annoying but it substantially more secure.

                This being said I think you can do it as root. I think this might work but I am not certain sudo systemctl --user -M theuser@ status myunit.service

        • Quik@infosec.pubEnglish
          3·
          3 天前

          Same here; Rootless Podman Quadlets gang unite (there is two of us in total)

      • Quik@infosec.pub
        2·
        3 天前

        Just place your Quadlets in the $HOME/.config/containers/systemd/ directory for this ;)

        The reference I linked to earlier also contains more information on rootless.

        • dwt@feddit.orgDeutsch
          1·
          2 天前

          While that is true, that is not how I would run services normally with SystemD. Those would be defined globally, but run as a user.

          Definitiv then in the user home, means that I dint see them with systemctl which is very annoying.

  • troed@fedia.io
    551·
    3 天前

    Unix grey beard here.

    Yes. Distros with systemd are simply easier to maintain.

      • Balinares@pawb.social
        141·
        3 天前

        Especially then. Great documentation and support tooling make troubleshooting much easier.

        • SheeEttin@lemmy.zipEnglish
          8·
          3 天前

          Can you give me a link to that documenation and tooling? Because every time I go to troubleshoot an issue, I end up in a tangled mess of trying to figure out how systemd and NetworkManager have decided to configure themselves on this particular system, and I give up.

          I don’t know how it happens, but I can set up Ubuntu on a dozen laptops in exactly the same way, and a week later they all have different configurations.

          • Balinares@pawb.social
            91·
            3 天前

            Can you give me a link to that documenation and tooling?

            Linux daemons and utilities typically come with manuals that get installed alongside the software. There’s a command line tool, aptly called man, that can be used to search and display these manuals. So for instance, man resolvectl displays the manual for the command line utility that you can use to control, configure, monitor and debug the systemd-resolved daemon. (Although I usually look up the man page online because it’s more convenient to scroll through than in a terminal.) Man pages for a given daemon will typically mention near the bottom related man pages for e.g. control utilities like resolvectl, so it’s not necessary to remember it by heart.

            a week later they all have different configurations.

            I’m trying to remember any situation where one of the systemd components would change its configuration on its own, but I’m coming up blank. It may be my memory failing me, but possibly that’s the wrong tree to bark up?

        • eutampieri@feddit.it
          4·
          3 天前

          Then I must be using it wrong. I kept systemd-resolved on my laptop but on my desktop I use plain old /etc/resolv.conf

  • Possibly linux@lemmy.zipEnglish
    2·
    2 天前

    No one cares about systemd at this point

    If you want to use your computer like it is 2005 go for it. Just don’t keep bringing up this dead topic.

  • Safeguard@beehaw.org
    201·
    3 天前

    I agree. For a init system.

    I don’t like the “takeover” of network and home folders. (It feels like a takeover for me)

  • ISO@lemmy.zip
    92·
    3 天前

    The first thing forcing an option does, is depriving that option the ability to know what it could achieve on pure merit.

  • Cris@lemmy.worldEnglish
    6·
    3 天前

    Systemd is fine but I am kinda sad that it’s ubiquity has resulted in increasing dependence on it.

    I really like void linux which uses runit and it seems like its getting harder for things to work without systemd. Gnome made some changes fairly recently that increase dependence, I hope devs can build ways for gnome to still work :/

    My only real criticism is that using runit makes me feel like systemd could be a lot smaller and more elegant. But using systemd has never caused me any problems as best I’m aware 🤷‍♂️

  • Sibbo@sopuli.xyz
    15·
    3 天前

    When I was starting to use Linux in the late 2010s, I was quite confused by how all the init stuff worked. Now that I use NixOS and systemd, I’m things have become really easy. I could write a simple backup system by chaining a few services together without problems.

    • Swedneck@discuss.tchncs.de
      263·
      3 天前

      Introducing: Being a contrarian asshat!
      Yes, by being a contrarian asshat you too can legitimately claim that any statement is disputed, because You dispute it!