• 0 Posts
  • 6 Comments
Joined 5 months ago
Cake day: October 13th, 2024
  • Asparagus0098@sh.itjust.workstoSelfhosted@lemmy.world•Question about quadlets and kube playEnglish
    3·
    2 days ago

    I ran a podman quadlet setup as a test some time ago. My setup was a little like this:

    • Create a pod if the app uses multiple containers
    • Create a seperate network for each app (an app is either a single container or multiple containers grouped in a pod)
    • Add the reverse proxy container to all networks
    • I don’t expose any ports to the host unless necessary

    If you create a new network in podman you can access other containers and pods in the same network with their name like so container_name:port or pod_name:port. This functionality is disabled in the default network by default. This works at least in the newer versions last I tried, so I have no idea about older podman versions.

    For auto-updates just add this in your .container file under [Container] section:

    [Container]
AutoUpdate=registry

    Now there’s two main ways you can choose to update:

    1. Enable podman-auto-update.timer to enable periodic updates similar to watchtower
    2. Run podman auto-update manually
    # Check for updates
podman auto-update --dry-run

# Update containers
podman auto-update