sonarr VS Docker Compose

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

Solutions are many, and could include Docker Compose, VS Code dev containers, Telepresence, Localstack or setting up temporary AWS accounts as a development environment for serverless applications.

Using Docker Compose to run Postgres and any third-party services locally provides a streamlined and consistent development environment. Developers can define services in a docker-compose.yml file, which enables them to configure and launch an entire stack with a single command. In this case, Postgres is encapsulated within a container with predefined configurations. Docker Compose also facilitates easy scaling, updates, and isolation of services, enhancing development efficiency and reducing the setup time for new team members or transitioning between projects. It encapsulates complex configurations, such as Postgres' performance monitoring and logging settings, in a manageable, version-controlled file, simplifying and replicating the service setup across different environments.

“Compose simplifies the control of your entire application stack, making it easy to manage services, networks, and volumes in a single, comprehensible YAML configuration file. Then, with a single command, you create and start all the services from your configuration file.” - Docker documentation

curl -fsSL https://get.docker.com -o get-docker.sh sudo sh get-docker.sh # Install docker compose sudo curl -L "https://github.com/docker/compose/releases/download/1.29.2/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose # Apply executable permissions to the binary sudo chmod +x /usr/local/bin/docker-compose # Run Project docker-compose up -d

Docker,

This foundation now opens the door to even more powerful concepts. You can explore more advanced concepts such as container networking, streamlining the management of complex applications with Docker Compose, and how to make your application data persistent using volumes.

In many projects that are containerized, especially in cases where development is also done locally with docker-compose, teams often have two Dockerfiles, 1 for Development, the other for Production. If you happen to have multiple environments like pre-prod, staging and so on, some teams could have different Dockerfiles for these environments.

sudo curl -L "https://github.com/docker/compose/releases/latest/download/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose