How to upgrade Sonarr from Docker?

From within Sonarr, System | Updates always worked for me.

I generally don't upgrade images unless there is some good reason to do so.

I use watchtower docker to update automatically my others dockers: https://hub.docker.com/r/v2tec/watchtower/

Quote from raulfg3

I use watchtower docker to update automatically my others dockers: https://hub.docker.com/r/v2tec/watchtower/

How do you get watchtower to cleanup the stale images though? I know there is a --cleanup option, but when I put that in the Extra args box it doesn't work. I think the extra args is for the docker daemon but this is an option for the watchtower container itself.

I clean up manually, from time to time.

I found a way to have it automatically cleanup stale images. I added a daily scheduled job through the OMV interface with the following command: docker images -q --filter "dangling=true" | xargs -n1 -r docker rmi

Seems to work!

Thanks a lot, I add it to my crom.

Quote from gammarayburst

I found a way to have it automatically cleanup stale images. I added a daily scheduled job through the OMV interface with the following command: docker images -q --filter "dangling=true" | xargs -n1 -r docker rmi

Seems to work!

This still works like a charm, thanks!

One question though: Do the arguments "-n1" and "-r" add any value? The command seems to work without them:
docker images -q --filter dangling=true | xargs docker rmi

I just use two docker containers and hence using watchtower is a little bit to much overhead for me. So I'm going the manual update route. However that's really easy using OMVs docker plugin. I'll desribe my methode for a emby update.

- First I check the emby repo if there are new instructions (to be able to make necessary changes later).
- Then I pull the new image (repo in this case emby/embyserver - tag: latest)
- When done I stop the running existing instance of emby.
- Then I click that instance to mark it and press the 'copy' button.
- Here I give the new container a new name (Emby4.0.2.0); in case of new instructions I adapt the config and save it
- Now start the new container and test if all is working.
- Last step would be a cleanup
Altogether that needs 2-3 minutes. If someting goes wrong you can just start the old version again.

--cleanup do not work for me.

Yes I know that supossed must work.

Quote from sNiXx

This still works like a charm, thanks!
One question though: Do the arguments "-n1" and "-r" add any value? The command seems to work without them:
docker images -q --filter dangling=true | xargs docker rmi

hello, it is better to use the native docker function

docker image prune -a

The -a parameter is the crucial bit here.

If you want to force the action to occur without a confirmation prompt, you may add the -f parameter, like so:

docker image prune -af