Automated media server alternates between NFS and DNS issues

[Grumpher]

Hi all,

Will preface this with I only have about a week of ubuntu/container experience, very new to this and been working through problems slowly but finally found one that doesn't seem to have the answer on google. I'm using podman-compose to run a stack of nginx, transmission, Plex, Radarr, Sonarr etc. My main issue at the moment is with Radarr and Sonarr combined with a NFS synology where my media is located, mounted to root using fstab then mounting that to the containers using compose.yml

My issue is after running compose, plex works fine and can access my media and the network. but radarr and sonarr can only access my media occasionally, and at those times I lose my ability to search, getting errors hostname errors for the servarr.com it tries to access to get to tmdb. after some reboots I can get the hostname to resolve and search can function, but then the media folders are missing. I'm not able to get both at the same time and I cannot determine any sort of reason becuase plex always works, but *arr's change with reboots without changing anything. One interesting caveat is that sonarr can at some level detect the NFS, as it will show the free space as 2 TB vs 30gb, but it is not able to actually show me my media files

using the guides from smarthomebeginners.com it goes through setting up the compose for docker, and then walks through how to configure it for podman instead of docker. below is my compose file. I'm not sure what other logs/files to include here to help diagnose
I would prefer to mount the NFS using the compose file but as far as I understand that isn't doable with a rootless container

########################### NETWORKS ###########################
# You may only customize the network subnet (192.168.89.0/24) below if you are using
# Podman-Compose version 1.0.4 or higher.

networks:
  npm_proxy:
    name: npm_proxy
    # ipam:
    #   config:
    #     - subnet: 192.168.89.0/24



########################### EXTENSION FIELDS
# Helps eliminate repetition of sections
# More Info on how to use this: https://github.com/htpcBeginner/docker-traefik/pull/228

# Common environment values
x-environment: &default-tz-puid-pgid
  TZ: $TZ
  PUID: $PUID
  PGID: $PGID

# Keys common to some of the core services that we always to automatically restart on failure
x-common-keys-core: &common-keys-core
  networks:
    - npm_proxy
  security_opt:
    - no-new-privileges
  restart: always

# Keys common to some of the dependent services/apps
x-common-keys-apps: &common-keys-apps
  networks:
    - npm_proxy
  security_opt:
    - no-new-privileges
  restart: unless-stopped

# Keys common to some of the services in media-services.txt
x-common-keys-media: &common-keys-media
  networks:
    - npm_proxy
  security_opt:
    - no-new-privileges
  restart: "no"

################################################
#################### SERVICES ##################
services:

    # Nginx Proxy Manager - Reverse Proxy with LetsEncrypt
  npm:
    <<: *common-keys-core # See EXTENSION FIELDS at the top
    container_name: nginx-proxy-manager
    # Use the fully qualified name to pull including the docker.io portion
    image: 'docker.io/jc21/nginx-proxy-manager:latest'
    # We will let Podman assign a Dynamic IP
    networks:
      - npm_proxy
    # If you REALLY need a static IP (normally not necessary) and are using podman-compose version <= 1.0.3,
    # you will need to create the npm_proxy network manually with podman, using the --subnet flag. If you've done that you can use the following:
    #  networks:
    #    npm_proxy:
    #      ipv4_address: 192.168.89.254
    ports:
      - '80:80' # Public HTTP Port. Port Forwarding on Router is ON.
      - '443:443' # Public HTTPS Port. Port Forwarding on Router is ON.
      - '81:81' # Admin Web Port. Port Forwarding on Router is OFF. Internal Home Network Access only.
    volumes:
      - $DOCKERDIR/appdata/npm/config:/config
      - $DOCKERDIR/appdata/npm/letsencrypt:/etc/letsencrypt
      - $DOCKERDIR/appdata/npm/data:/data
    environment:
      DB_SQLITE_FILE: "/config/database.sqlite"
      DISABLE_IPV6: 'true'
##################################      DOWNLOADERS

  # Radarr - Movie management
  radarr:
    <<: *common-keys-media # See EXTENSION FIELDS at the top
    image: lscr.io/linuxserver/radarr:nightly # latest tag was causing "Error parsing column 45"
    container_name: radarr
    dns:
      - 8.8.8.8
    networks:
      - npm_proxy
       # ipv4_address: 192.168.89.164
    ports:
      - "7878:7878"
    volumes:
      - $DOCKERDIR/appdata/radarr:/config
      - $WYSENAS/radarr/downloads:/media/downloads
      - $MOVIEDIR:/NAS/movies
      - "/etc/localtime:/etc/localtime:ro"
    environment:
      <<: *default-tz-puid-pgid

  # Sonarr - TV Shows management
  sonarr:
    <<: *common-keys-media # See EXTENSION FIELDS at the top
    image: lscr.io/linuxserver/sonarr
    container_name: sonarr
    dns:
      - 8.8.8.8
    networks:
      - npm_proxy
       # ipv4_address: 192.168.89.167
    ports:
      - "8989:8989"
    volumes:
      - $DOCKERDIR/appdata/sonarr:/config
      - $WYSENAS/sonarr/downloads:/data/downloads
      - $TVDIR:/NAS/TV
      - "/etc/localtime:/etc/localtime:ro"
    environment:
      <<: *default-tz-puid-pgid


################################   Media Server
# Plex - Media Server
  plexms:
    <<: *common-keys-media # See EXTENSION FIELDS at the top
    image: plexinc/pms-docker:public
    container_name: plexms
    ports:
      - "32400:32400/tcp"
      - "3005:3005/tcp"
      - "8324:8324/tcp"
      - "32469:32469/tcp"
      - "1900:1900/udp" # Conflicts with xTeVe and Synology default ports
      - "32410:32410/udp"
      - "32412:32412/udp"
      - "32413:32413/udp"
      - "32414:32414/udp"
     # - "33400:33400" # If you use Plex Web Tools
    devices:
      - /dev/dri:/dev/dri # for harware transcoding
    volumes:
      - $DOCKERDIR/appdata/plexms:/config
      - $TVDIR:/NAS/TV
      - $MOVIEDIR:/NAS/movies
      - /dev/shm:/transcode
    environment:
      TZ: $TZ
      HOSTNAME: "dockerPlex"
      PLEX_CLAIM_FILE: $PLEX_CLAIM
      PLEX_UID: $PUID
      PLEX_GID: $PGID
      ADVERTISE_IP: http://$SERVER_IP:32400/

[Luap99]

Can you provide the output of podman info?

[Grumpher]

So is there anything specific I need to change to use netavark, or will it occur through using V 4.X podman with my current compose file?

Sorry if these seem silly questions, trying to wrap my head around a whole new ecosystem, appreciate the help!

[Luap99]

once podman 4.X, netavark and aardvark-dns are installed run podman system reset, then run podman info --format {{.Host.NetworkBackend}} to make sure it shows netavark.

[Grumpher]

reading up on updating podman has lead me down another rabbit hole, I see that for ubuntu, the package version available is 3.4.4 according to https://podman.io/blogs/2022/04/05/ubuntu-2204-lts-kubic.html

am I expected to follow some other member suggestions for getting a new version, looks to be something called homebrew to resolve the issue I'm having with networking? as far as I can tell I am on the latest officially supported version

[rhatdan]

Ununtu does not update versions during a Release as far as I know. So yes you would need to update the version from a community REPO if you want to get a version of Podman other then the default from the distribution.

[wcasanova]

reading up on updating podman has lead me down another rabbit hole, I see that for ubuntu, the package version available is 3.4.4 according to https://podman.io/blogs/2022/04/05/ubuntu-2204-lts-kubic.html

am I expected to follow some other member suggestions for getting a new version, looks to be something called homebrew to resolve the issue I'm having with networking? as far as I can tell I am on the latest officially supported version

Kubic project provides updated packages for several distros, specifically for Ubuntu kubic xUbuntu 22.04 podman-4:4.3.1-0ubuntu22.04