GitHub - beatkind/watchtower: A process for automating Docker container base image updates.
github.com
A process for automating Docker container base image updates. - GitHub - beatkind/watchtower: A process for automating Docker container base image updates.
  • @roofuskitEnglish
    5•5 hours ago

    Those of you self hosters who use watchtower, what’s your use case?

    • MorethanevilEnglish
      4•5 hours ago

      I only let me notify about updates. I don’t want autoupdates, because some projects may have breaking changes (looking at you Immich 😁)

      I get a message from watchtower over Gotify and then I can read the changelog

      • @blazeknaveOPEnglish
        2•5 hours ago

        I’ve been thinking about this. Can you do that with watchtower? Don’t need diem or anything?

        • MorethanevilEnglish
          1•4 hours ago

          It is very easy. Here is my compose:

          services:
  watchtower:
    image: containrrr/watchtower
    container_name: watchtower
    restart: always
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /etc/localtime:/etc/localtime:ro
    command: --interval 10800
    logging:
      driver: local
    environment:
          WATCHTOWER_NOTIFICATION_URL: gotify://
          WATCHTOWER_NOTIFICATIONS_HOSTNAME: Fancy name
          WATCHTOWER_MONITOR_ONLY: true
          WATCHTOWER_WARN_ON_HEAD_FAILURE: never

          Every 3 hours it will check for updates, send a message via Gotify and pull the new images. It will not restart the containers with the new images.

    • @[email protected]English
      3•5 hours ago

      Automatic updates. Works like a dream. Depending on what you are running it can obviously cause issues, either server side breaking or server,client communication issues

    • @blazeknaveOPEnglish
      2•5 hours ago

      ADHD and not technical by trade so it’s not in my DNA to remember

  • BlackEcoEnglish
    3•5 hours ago

    The first one also has better code coverage and way more pulls on Docker Hub.

    • @blazeknaveOPEnglish
      1•5 hours ago

      I don’t know. Last time I used it was maintained. Seems like a security vulnerability running something this critical out of date, no?

      • @[email protected]English
        2•4 hours ago

        Just because there is no update does not mean there are security vulnerabilities to worry about, or do you have a specific one that is not fixed?

        The attack vector seems very narrow to me. It checks the container registry downloads the containers and runs some docker commands.

        It has no interface, so in order to attack it you either have to compromise the container registry (but then it would be easier to compromise the containers you download) the secure connection used to download the containers (https is quite stable) or something on the server side.

        Also the project does not really look that abundant to me.

        EDIT: So i have not checked this, but watchtower is probably using docker for most steps anyway? So basically the only thing that could be attacked is via the notifications watchtower is sending?