@dont - eviltoast
  • 1 Post
  • 8 Comments
Joined 6 months ago
cake
Cake day: May 24th, 2024

help-circle



  • dont@lemmy.worldOPtoSelfhosted@lemmy.worldThe purpose of podman quadlets?
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 month ago

    Awesome, so, essentially, you create a name.pod file like so:

    [Unit]
    Description=Pod Description
    
    [Pod]
    # stuff like PublishPort or networking
    

    and join every container into the pod through the following line in the .container files: Pod=name.pod

    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?

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




  • Understood, thanks, but if I may ask, just to be sure: It seems to me that without interacting with the kubernetes layer, I’m not getting pods, only standalone containers, correct? (Not that I’m afraid of writing kube configuration, as others have inferred incorrectly. At this point, I’m mostly curious how this configuration would be looking, because I couldn’t find any examples.)


  • Thank you for those very convincing points. I think I’ll give it a try at some point. It seems to me that what you’re getting in return for writing quadlet configuration in addition to the kubernetes style pod/container config is that you don’t need to maintain an independent kubernetes distro since podman and systemd take care of it and allow for system-native management. This makes a lot of sense.