Programs Not Being Saved To The Directory I Choose

Channels DVR Server
#1

At one point had Channels DVR working great. Then ran into issues with the app & I moved. For whatever reason when I connected my server up to the new IP nothing worked. I am running Truenas Scale & I basically had to go back & install all my apps again. In order to get things working. The Channels DVR app for Truenas is complete garbage. Four about a year I was unable to add a new source. Now the last 2 or 3 updates will not even install.

Because I could not add a new source I had Channels DVR running a Win10 VM which worked fine. However, since I have moved, this no longer works. I cannot get the VM without using Tailscale which is a pain. I still utilize this instance if there is something that I want to keep. Because I know where these recording are being stored.

I have another instance of Channels DVR running in Portainer & that is my main instance. I cannot figure out how to set this up. In a way that I can see my recordings in the SMB folder that I choose when I setup channels DVR. I don't know what I am doing wrong. Yesterday, I tried adding a new "stack" in Portainer. When I started Channels DVR & was prompted to choose the folder for storage. My pool came up, however when I tried recoding something. It was not saved in that folder. Which begs the question, where are my recording going. I would really appreciate it if someone could help get me on the right path.

#2

First, I’m probably not gonna be that much helping.

Since you’re using Portainer, copy and post your stack compose plus a copy of your environment variables. The easiest , at least for me, is to go to your stack in Portainer and select the editor. There will be a copy to clipboard thumbnail on the right side for both the compose stack and the environment variables. Use advanced mode for the environment variables. Post those and I’m sure you’ll get some better assistance.

#3

What did your logs say?

#4

My current instance that is running was setup in a container & not a stack. This is probably part of my issue. I'll go back & install another instance of channels in a stack again. I just deleted the last one out of frustration. My compose yaml is below.

services:
  channels-dvr:
    image: fancybits/channels-dvr:TVE
    container_name: channels-dvr
    # Use 'host' networking for proper client discovery on a local network
    network_mode: host
    restart: unless-stopped
    environment:
      # Set your timezone, e.g., America/Los_Angeles
      - TZ=America/Chicago
    volumes:
      # Mount a local directory for Channels DVR configuration and data
      - /mnt/JAD01-Pool/app_data/Channeles_dvr_new
      # Mount a local directory for recordings
      - /mnt/JAD01-Pool/DVR_Recordings
#5

With the above approach, the only thing you're specifying are random paths INSIDE the container. Those paths will be bound to anonymous Docker Volumes. The path Channels uses inside containers for its app data, /channels-dvr, isn't even in the mix.

I doubt this is what you are intending. If that recordings path is a mount point in your Linux filesystem -- and you want it to have the same name inside the container try this:

    volumes:
      - /mnt/JAD01-Pool/app_data/Channeles_dvr_new:/channels-dvr
      - /mnt/JAD01-Pool/DVR_Recordings:/mnt/JAD01-Pool/DVR_Recordings

Obviously Channeles_dvr_new is a misspelling, but I'm assuming you intended that. Otherwise, I believe with that section changed, things should be more along the lines of what you had in mind.

#6

Thanks! I'll give it a shot tomorrow when I actually have some time. I ran into the same exact issue when I was able to get the Truenas app installed.

I'll see what happens.

#7

Thank you so much. That did work. I figured it was something easy that I was just doing wrong.

#8