• 0 Posts
  • 10 Comments
Joined 2 months ago
cake
Cake day: October 13th, 2024

help-circle





  • Yeah quadlets are pretty cool. I have them organized into folders for each pod. podman auto-update is also another pretty nice feature. I don’t use the systemd timer for auto-update. Instead I just do podman auto-update --dry-run to check for updates and update my quadlet files and configs if any changes are required then I run the updates with podman auto-update.




  • Asparagus0098toSelfhosted@lemmy.worldPodman or rootless docker?
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    1 month ago

    Do you mean networking between them? There’s two ways of networking between containers. One of them is to create a custom network for a set of containers that you want to connect between each other. Then you can access other containers in that network using their name and port number like so

    container_name:1234
    

    Note: DNS is disabled in the default network by default so you can’t access other containers by their name if using it. You need to create a new network for it to work.

    Another way is to group them together with a pod. Then you can access other services in that same pod using localhost like so

    localhost:1234
    

    Personally in my current setup I’m using both pods and seperate networks for each of them. The reason is I use traefik and I don’t want all of my containers in a single network along with traefik. So I just made a seperate network for each of my pods and give traefik access to that network. As an example here’s my komga setup:

    I have komga and komf running in a single pod with a network called komga assigned to the pod. So now I can communicate between komga and komf using localhost. I also added traefik to the komga network so that I can reverse proxy my komga instance.