Comment

Comment on I'm using compose wrong and I know it.

This is what I use whenever I make my own services or am using a simple service with only one container. But I have yet to figure out how to convert a more complicated service like lemmy that already uses docker-compose, so I just use podman-docker and emulate docker-compose with podman. But that doesn’t get me any of the benefits of systemd and now my podman has a daemon, which defeats one of the main purposes of podman.

source

Sort:hotnew top

poVoq@slrpnk.net ⁨1⁩ ⁨year⁩ ago
Just forget about podman-compose and use simple Quadlet container files with Systemd. That way it is not all in the same file, but Systemd handles all the inter-relations between the containers just fine.

Alternatively Podman also supports kubernetes configuration files, which is probably closer to what you have in mind, but I never tried that myself as the above is much simpler and better integrated with existing Systemd service files.

source
- vegetaaaaaaa@lemmy.world ⁨1⁩ ⁨year⁩ ago
  
  Quadlet
  
  Requires podman 4.4 though
  
  source
  - poVoq@slrpnk.net ⁨1⁩ ⁨year⁩ ago
    No, from that version on, it is integrated in Podman, but it was available for earlier versions as a 3rd party extension as well.
    
    But if you are not yet on Podman 4.4 or later you should really upgrade soon, that version is quite old already.
    
    source
    vegetaaaaaaa@lemmy.world ⁨1⁩ ⁨year⁩ ago
    
    you should really upgrade soon
    
    Debian stable has podman 4.3 and 4.4 is not in stable-backports
    
    source
exu@feditown.com ⁨1⁩ ⁨year⁩ ago
You can use podman pods and generate the systemd file for the whole pod.

source
- dandroid@dandroid.app ⁨1⁩ ⁨year⁩ ago
  But how do I convert the docker-compose file to a pod definition? If I have to do it manually, that’s a pass because I don’t want to do it again if lemmy updates and significantly changes it’s docker-compose file, which it did when 0.18.0 came out.
  
  source