• shiftymccool@programming.dev
    link
    fedilink
    English
    arrow-up
    4
    ·
    2 months ago

    Not sure why Renovate is necessary when Komodo has built-in functionality to update Docker images/containers. I wish there was an option to check less often (like once a day), maximum time is hourly.

    Also, if you’re using Komodo and have one big repo of compose files, consider just saving your entire config toml to a repo instead. You end up with something akin to Terraform or Cloudformation for your Docker hosts

    • tofu@lemmy.nocturnal.gardenOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      I haven’t used Komodo yet, does it change the compose files in the repo as well? I thought it’s just reading, not writing. Personally I like the workflow of Merge Requests that Renovate provides.

      Not sure what you mean with the second paragraph. Which config toml?

  • mbirth@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    I’ve just set WatchTower to one-shot runs and whenever I have some time to fix eventual issues, I start the WatchTower container, it’ll pull any updates and stop again. No need to mess with my compose files (all set to latest) and no need for pull requests or similar.

    • spacegoat@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      Interesting. Can you clarify what you meant by one-shot runs?

      I have watchtower running all the time, would it be worth it/is it best practice to stop it