• talentedkiwi@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    29 days ago

    Did you use docker compose file or just run a command to start the container?

    Edit: I always use compose files. For that you can do the following:

    docker compose pull
    docker compose down
    docker compose up -d
    

    You don’t technically need the stop, but I’ve found once or twice in the past where it was good to stop because of image dependencies that I forgot to put in my compose.

    For running a command directly I found this website that seems to summarize it pretty well I think:

    https://www.cherryservers.com/blog/how-to-update-docker-image

    • M600@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      29 days ago

      Yes, I used docker compose. Do I need to do anything to clean up with this method?

      • talentedkiwi@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        29 days ago

        Now that you mention it, I always do a

        docker system prune -f
        

        This will clean up old images that are no longer used. I setup an alias command in Linux to do all of those commands.

        I just named it docker_update and saved it in my ~/.bashrc

        alias docker_update="docker compose pull && docker compose down && docker compose up -d && docker system prune -f"
        
        • talentedkiwi@sh.itjust.works
          link
          fedilink
          arrow-up
          0
          ·
          29 days ago

          I see someone mention watchtower, while not a bad thing, I just prefer to manually update. This helps to ensure any breaking changes don’t break my system. Especially with something like Immich at it’s had a lot of them recently as they work towards stable. I just generally subscribe to their release and do updates as necessary.