• 4 Posts
  • 36 Comments
Joined 5 months ago
cake
Cake day: June 23rd, 2024

help-circle

  • “I confess, I did not know who Pete Hegseth was until about 20 minutes ago,” Smith told reporters.

    “He does not seem to have much of a detailed background in [Department of Defense] policy. To the extent he’s worked on any of that stuff, it has been on veterans policy, not on DoD issues. So the lack of experience is concerning,” Smith said.

    “Now I have not heard what his plans are, so we will see what his plans are,” he added. “But it was surprising and is concerning, just given that lack of experience. You know, the Pentagon, biggest bureaucracy in the world. It’s a hard thing to run, so I think it’s going to be a challenge."

    In the words of Wash: Oh god, oh god, we’re all gonna die.



















  • Awesome, so, essentially, you create a name.pod file like so: […]and join every container into the pod through the following line in the .container files

    Yep, that’s the way!

    and I presume this all gets started via systemctl --user start name.service and systemd/podman figures out somehow which containers will have to be created and joined into the pod, or do they all have to be started individually?

    Systemd figures it out iff you have specified your service dependencies correctly, with things like After=, Upholds=, BindsTo=, etc. Have a look at systemd.unit manpage for details. For my paperless service, it goes something like this:

    1. The entrypoint is paperless.container, which I start with systemctl --user start paperless, which depends on:
      • paperless.pod
      • Three other services, which also depend on:
        • paperless.pod
    2. Systemd figures out that the paperless pod should be started first, and does that
    3. Systemd startes the three dependent containers
    4. Finally, systemd starts the paperless container itself

    The point of quadlet was to lean as heavily as possible on systemd for the service and dependency bits and use podman only for translating the container bits into something systemd can handle. The one bit of dependency handling that quadlet does is to make sure that paperless.pod is started before all containers that have Pod=paperless.pod in their quadlet file.

    Either way, I find the documentation of this feature lacking. When I tested this stuff myself, I’ll look into improving it.

    That would be amazing, of course! :) I find that, if you’re familiar with unit files, you’re like 85% of the way there already. By the way, the unit files that quadlet generates are somewhere in $XDG_RUNTUME_DIR for you to inspect. I’m afraid I’m not at a computer right now andI don’t know the exact path off the top of my head.