Is it safe to automatically pull and update docker containers?

Comments

• SteadyGoLucky@sh.itjust.works ⁨4⁩ ⁨months⁩ ago

  Some apps have breaking changes. If you can restore a complete backup when that occurs, you can recover. Immich is famous for its breaking changes

  source

  • peregus@lemmy.world ⁨4⁩ ⁨months⁩ ago

    But from the moment that the script updates and breaks something and the moment he realizes it may be too late for some applications.

    For example I host Traccar to track car/vans and in this case some tracks would be lost. Or maybe SyncThing, he may realize days/weeks later that a sync is not working and if he was synching his smartphone pictures with his server and the smartphone is lost/broke/stolen, he may lose days/weeks or even months of pictures.

    I wouldn’t trust a script. Use Watchtower or What’s up Docker

    @tubbadu@lemmy.kde.social

    source

    • tritonium@midwest.social ⁨4⁩ ⁨months⁩ ago

      That’s why you you bind mount all the imports shit and back it up. And why you also have a monitoring and notification system that alerts you if a service goes down. I will get a telegram message within 15 minutes of a service going down. And have backups of everything with borg

      source

      • -> View More Comments
    • tubbadu@lemmy.kde.social ⁨4⁩ ⁨months⁩ ago

      I’ll surely check them out, thank you very much!

      source
  • ShortN0te@lemmy.ml ⁨4⁩ ⁨months⁩ ago

    Yes because immich is still not considered stable. Keep that in mind.

    source
• wjs018@lemmy.world ⁨4⁩ ⁨months⁩ ago

  I used to have my docker updates done automatically. However, as the services I used to run just for myself have started to be used by other people (family, friends), I am less tolerant of having things break. So, instead of something like watchtower, I run diun these days. I have it set up to ping me in a discord channel when a docker update is available. Then, I can actually perform the update when I have time and attention to troubleshoot any issues that may come up.

  source

  • earth_walker@lemmy.world ⁨4⁩ ⁨months⁩ ago

    Agree, if you are running containers on a casual or “just for fun” basis then automatic updates are fine. But the more you or others depend on the service running, the more it makes sense to perform an update manually, when you have time to troubleshoot any problems that may arise. Or, even update on a test setup first to identify issues and then update on your production setup.

    source
• atzanteol@sh.itjust.works ⁨4⁩ ⁨months⁩ ago

  Depends on how you like to roll. If you enjoy waking up to a service not working then go for it.

  But it very much depends on what containers you’re using and what tags you’re pulling.

  source
• redxef@feddit.de ⁨4⁩ ⁨months⁩ ago

  I get a summary once a week of all the updates. I then check the release notes and if nothing needs any changes just run the ansible playbook that updates to those releases. I don’t want to get up and first thing in the morning read alert emails because an update failed over night, so i sit down for 10 minutes once a week.

  source
• JASN_DE@lemmy.world ⁨4⁩ ⁨months⁩ ago

  I run a mixed setup, many of the “less important” containers are on watchtower auto-update, the rest on notification (reverse proxy, Nextcloud, etc).

  But I also have many of them on specific branches instead of “latest”.

  source
• ShortN0te@lemmy.ml ⁨4⁩ ⁨months⁩ ago

  I recommend, reading the release changelogs actively. For most services you can just put the github release page in an RSS reader to get a notification when a new release hits, so you can quickly look for any breaking changes, also this will give you info about new features.

  I have been using watchtower for a few years. No problems with auto updates so far, but keep your backup handy.

  source
• BrightCandle@lemmy.world ⁨4⁩ ⁨months⁩ ago

  It really depends on the project. Some of them take breaking changes seriously and don’t do them and auto migrate and others will throw them out on “minor” number releases and there might be a lot of breaking changes but you only run into one that impacts you occasionally. I typically don’t want containers that are going to be a lot of work to keep up to date so I jettison projects that have unreliable releases for whatever reason and if they put out a breaking change its a good time to re evaluate whether I want that container at all and look at alternatives.

  So no its not safe, but depending on the project it actually can be.

  source
• MangoPenguin@lemmy.blahaj.zone ⁨4⁩ ⁨months⁩ ago

  No, but you should already have good backups in place (right??) so restoring if something breaks isn’t too hard.

  source
• GravitySpoiled@lemmy.ml ⁨4⁩ ⁨months⁩ ago

  That’s what I do as well. Even with immich. It may break but it’s usually just a simple change in the env file

  source
• Konraddo@lemmy.world ⁨4⁩ ⁨months⁩ ago

  Depends on the application really. For example, I don’t need to update Jellyfin and the arrs as soon as the new updates drop. They work just fine and I’m not waiting for any particular fixes.

  source
• Oisteink@feddit.nl ⁨4⁩ ⁨months⁩ ago

  Basically why i feel more comfortable with LXC than docker for my home lab services. It feels more like a VM in management.

  source
• catloaf@lemm.ee ⁨4⁩ ⁨months⁩ ago

  I’ve been doing it for a few years and haven’t had any issues. The risk/reward decision is yours.

  source
• anzo@programming.dev ⁨4⁩ ⁨months⁩ ago

  I’m using github.com/mag37/dockcheck for this, with its “-d N” argument. There’s a tradeoff between stability and security, you need to decide for yourself. It will also depend on what services you’re hosting. For example, nextcloud and immich would be disastrous under such a regime.

  source