0

I'm running docker on PopOS. I had a nice media stack as you can see here, although that's an old link, it's still the jist. Moved from overseerr -> ombi and plex -> emby.

So, I'm on the fresh install of PopOS, use mergerfs to pool my drives, etc.. inspired mostly by Perfect Media Server.

I ran docker-compose up -d and everything looked good... except a few applications. I'll give sonarr as an example.

It's web interface would not come up, so I ran docker logs sonarr and found this repeating over and over again.

You can find the sonarr logs here.

In my docker-compose.yml, I use the following to set up my image:

sonarr:
image: linuxserver/sonarr
container_name: sonarr
restart: always
ports:
  - "8989:8989"
networks:
  - plexnet
environment:
  - PGID=${PGID}
  - PUID=${PUID}
  - TZ=${TIMEZONE}
volumes:
  - ${MOUNT_POINT}/transmission:/data
  - ${MOUNT_POINT}/sonarr/config:/config
  - ${MOUNT_POINT}/sma:/usr/local/sma/config
  - ${MOUNT_POINT}/plex/tv:/tv
  - ${MOUNT_POINT}/transmission/completed:/downloads

I have deleted all sonarr images, removed the containers downloaded other version of sonarr, delete all files/folder associated with sonarr, and yet it still give the output you see here.

I can't imagine what is going on and how any configuration data is preserved.

Emby, Jackett, Transmission, and Tdarr all work perfectly. All other images have a problem with this clean install.

Gerald
  • 101
  • don't use nopaste services for nesesscary information, format it correctly and it's fine. Use your backups and restore it. – djdomi Jul 05 '22 at 17:06

0 Answers0