sonarr VS Medusa

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

You can learn more about Medusa by checking their GitHub repository.

Hello, I'm Nick, co-founder of Medusa. In keeping with our tradition, we are excited to share our progress on our open-source commerce SDK with this wonderful community. We eagerly want your feedback!

If you have everything installed, follow these steps to set up your Medusa project.

As the world moves towards a more digital economy, e-commerce is becoming an increasingly important part of businesses. To keep up with the changing times, it’s essential to adopt a cloud-native approach to your e-commerce platform. In this blog, we will introduce you to two powerful tools that can help you achieve rapid deployment of your e-commerce website: Microtica and Medusa.js. We will take a deep dive into what cloud-native e-commerce is, how Microtica and Medusa.js work, and how they complement each other. We will also discuss case studies of successful deployment using these tools and what skills are required for implementing them. Lastly, we’ll talk about future trends in cloud-native e-commerce and how Microtica and Medusa.js shape the future of online shopping.

The Medusa Next.js Starter Template supports popular instant-search providers Melliseach and Algolia out of the box. With these integrations, you can provide fast and accurate search results.

Co-founder of Medusa, here.

Co-founder of Medusa here; building blocks for digital commerce.

Hi - I'm Nick, co-founder of MedusaJS.

Nick, co-founder of Medusa, here. As per tradition now, we love to share the progress we make on our open-source commerce SDK with this amazing community. Always keen to hear your feedback!