sonarr VS watchtower

I saw the command. I feel line --user is the culprit. Haven't seen that flag before. Anyways, I'd suggest follow the official Hotio docs: https://hotio.dev/containers/sonarr/

I transitioned to the following image for the time being - https://hotio.dev/containers/sonarr/

I use Hotio's, which is pretty much comparable.

So the (official?) Sonarr repo ( https://github.com/Sonarr/Sonarr/tags ) lists main version v3 as the latest there isn't even a mention of v4 at all. However, Hotio does have a v4 ( https://hotio.dev/containers/sonarr/ ) and if you spin it up it is indeed v4 in the system settings etc.

I'm not sure, I used docker image: cr.hotio.dev/hotio/sonarr:v4 https://hotio.dev/containers/sonarr/

It's currently in development/pre-release, you can use the v4 tag on hotio/sonarr Docker images if you want to play around with it.

version: "3.2" services: # Radarr - https://hotio.dev/containers/radarr/ # radarr: container_name: radarr image: ghcr.io/hotio/radarr:latest restart: unless-stopped logging: driver: json-file network_mode: bridge ports: - 7878:7878 environment: - PUID=${PUID} - PGID=${PGID} - TZ=${TZ} volumes: - /etc/localtime:/etc/localtime:ro - ${DOCKERCONFDIR}/radarr:/config - ${DOCKERSTORAGEDIR}:/data # Sonarr - https://hotio.dev/containers/sonarr/ # sonarr: container_name: sonarr image: ghcr.io/hotio/sonarr:nightly restart: unless-stopped logging: driver: json-file network_mode: bridge ports: - 8989:8989 environment: - PUID=${PUID} - PGID=${PGID} - TZ=${TZ} volumes: - /etc/localtime:/etc/localtime:ro - ${DOCKERCONFDIR}/sonarr:/config - ${DOCKERSTORAGEDIR}:/data # Bazarr - https://hotio.dev/containers/bazarr/ # bazarr: container_name: bazarr image: ghcr.io/hotio/bazarr:nightly restart: unless-stopped logging: driver: json-file network_mode: bridge ports: - 6767:6767 environment: - PUID=${PUID} - PGID=${PGID} - TZ=${TZ} volumes: - /etc/localtime:/etc/localtime:ro - ${DOCKERCONFDIR}/bazarr:/config - ${DOCKERSTORAGEDIR}/media:/data/media # Watchtower (automatic docker container updater) - https://github.com/containrrr/watchtower watchtower: container_name: watchtower image: containrrr/watchtower restart: unless-stopped logging: driver: json-file network_mode: bridge environment: - PUID=${PUID} - PGID=${PGID} - TZ=${TZ} - UMASK=022 - WATCHTOWER_CLEANUP=true - WATCHTOWER_INCLUDE_STOPPED=false - WATCHTOWER_MONITOR_ONLY=false - WATCHTOWER_SCHEDULE=0 0 4 * * * - WATCHTOWER_TIMEOUT=10s volumes: - /etc/localtime:/etc/localtime:ro - /var/run/docker.sock:/var/run/docker.sock Plex - https://hotio.dev/containers/plex/ plex: container_name: plex image: ghcr.io/hotio/plex restart: unless-stopped logging: driver: json-file network_mode: bridge ports: - 32400:32400 environment: - PUID=${PUID} - PGID=${PGID} - TZ=${TZ} - UMASK=002 - ARGS= - DEBUG=no - PLEX_CLAIM=${PLEX_CLAIM} - ADVERTISE_IP= - ALLOWED_NETWORKS= - PLEX_PASS=${PLEX_PASS} volumes: - /etc/localtime:/etc/localtime:ro - ${DOCKERCONFDIR}/plex:/config:rw - ${DOCKERSTORAGEDIR}/media:/data/media:rw - /tmp:/transcode:rw - /dev/dri:/dev/dri # Tautulli - https://hotio.dev/containers/tautulli/ # tautulli: container_name: tautulli image: ghcr.io/hotio/tautulli restart: unless-stopped logging: driver: json-file network_mode: bridge ports: - 8181:8181 environment: - PUID=${PUID} - PGID=${PGID} - TZ=${TZ} - UMASK=002 - ARGS= - DEBUG=no volumes: - /etc/localtime:/etc/localtime:ro - ${DOCKERCONFDIR}/tautulli:/config:rw # NZBGET - https://hotio.dev/containers/nzbget/ # nzbget: container_name: nzbget image: ghcr.io/hotio/nzbget:release restart: unless-stopped logging: driver: json-file network_mode: bridge ports: - 6789:6789 environment: - PUID=${PUID} - PGID=${PGID} - TZ=${TZ} - UMASK=002 volumes: - /etc/localtime:/etc/localtime:ro - ${DOCKERCONFDIR}/nzbget:/config - ${DOCKERSTORAGEDIR}:/data overseerr: container_name: overseerr image: sctx/overseerr restart: unless-stopped logging: driver: json-file network_mode: bridge ports: - 5055:5055 environment: - PUID=${PUID} - PGID=${PGID} - TZ=${TZ} - UMASK=002 volumes: - /etc/localtime:/etc/localtime:ro - ${DOCKERCONFDIR}/overseerr:/app/config

hotio/Sonarr:release

Related: https://github.com/containrrr/watchtower

> if you're using the docker image, upgrades are a breeze. Just bump the tag on the image, redeploy, and you're done.

Or you could just run Watchtower beside it and it will automatically update your docker containers. https://github.com/containrrr/watchtower If you are OK with automated updates.

So i primarily use containers on my local machine walled off from the internet, so it's not a big concern for me. Watchtower [1] is popular among home server users too which automatically updates containers to the latest image.

For production uses I think companies generally build their own containers. They would have a common base linux container and build the other containers based off that with a typical CI/CD pipeline. So if glibc is patched, it's probably patched in the base container and the others are then rebuilt. You don't have to patch each container individually, just the base. Production also minimizes the scope of containers with nothing installed except what's necessary so they have few dependencies.

[1] https://github.com/containrrr/watchtower

You can use Watchtower (https://containrrr.dev/watchtower/) that solves problem of manual pulling on VPS.

I checked https://containrrr.dev/watchtower/ and Arguments, but I don't understand where to attach that using portainer.

Again, there are options to automate some of the burden here by using tools such as Watchtower.

Have you ever deployed a Docker app on a server, but everytime you push a new version of your image to a Docker registry you need to manually restart your app? If you want to automate this restarting, this blog post is for you! I am now going to show you how you can do this with literally 1 simple command using Watchtower!