NextPVR Forums
  • Home
  • New Posts
  • Wiki
  • Members
  • Help
  • Search
  • Register
  • Login
  • Home
  • Wiki
  • Members
  • Help
  • Search
NextPVR Forums Public NextPVR v5 Support Docker amd64 v
« Previous 1 2 3 4 Next »
Help with Open Media Vault docker install.

 
  • 0 Vote(s) - 0 Average
Help with Open Media Vault docker install.
Me123
Offline

Junior Member

USA
Posts: 4
Threads: 1
Joined: May 2020
#1
2020-05-31, 05:25 PM (This post was last modified: 2020-05-31, 10:12 PM by Me123.)
Hello, 
I have just recently set up a Open Media Vault NAS and I am having trouble trying to figure out how to install the docker.

I tried using stacks in Portainer but I am getting this error. "Deployment error unsupported compose file version 1.0"

This was my attempt.

nextpvr:
    image: nextpvr/nextpvr_amd64Confusedtable
    container_name: nextpvr
    network_mode: host
    environment:
      - PUID=998
      - PGID=100
      - TZ=America/Los_Angeles
volumes:
    -/srv/dev-disk-by-label-Media/one/nextpvr/config:/config \
    -/srv/dev-disk-by-label-Media/one/nextpvr/videos:/recordings \
    -/srv/dev-disk-by-label-Media/one/nextpvr/buffer:/buffer \ 
ports:
  - "8866:8866"
restart: unless-stopped 


I am totally lost on how to deploy the docker container and I have no clue how to install it as I am brand new to all of this,
my aging brain is probably not helping. I can pull the docker image and it shows up in my images but I don't know how to configure it.


Thanks.

OK, I got rid of the compose file version error by adding a version: "3" line at the top and now get a new error "volumes must be a mapping" I thought that was what I was doing with
volumes:
    -/srv/dev-disk-by-label-Media/one/nextpvr/config:/config \
    -/srv/dev-disk-by-label-Media/one/nextpvr/videos:/recordings \
    -/srv/dev-disk-by-label-Media/one/nextpvr/buffer:/buffer \

which are shared folders I setup and the absolute path.

I tried using putty with the 
docker run -d \
    --volume /srv/dev-disk-by-label-Media/one/nextpvr/config:/config \               
    --volume /srv/dev-disk-by-label-Media/one/nextpvr/videos:/recordings \
    --volume /srv/dev-disk-by-label-Media/one/nextpvr/buffer:/buffer \
    --publish 8866:8866 \
    nextpvr/nextpvr_amd64:latest

and get "docker: invalid reference format."
Ranbato
Offline

Junior Member

Utah
Posts: 48
Threads: 7
Joined: Nov 2018
#2
2020-06-01, 08:40 PM
Here is my old docker script for my Synology NAS
Code:
sudo docker run -d --name nextpvr --restart unless-stopped \
--volume /volume1/config/nextpvr/config:/config  \
--volume /volume1/video/nextpvr/recordings:/recordings \
--volume /volume1/video/nextpvr/buffer:/buffer \
--volume /volume1/video/Video:/kodi \
--publish 8866:8866 \
--env HOST_IP=192.168.1.140 \
--env PUID=1024 \
--env PGID=100 \
--env TZ='America/Denver' \
--publish 8020-8030:8020-8030/udp \
--device /dev/dri:/dev/dri  \
nextpvr/nextpvr_amd64:latest

I use docker-compose now but am running a number of images.  I have an additional mapping and a hardware mapping, but should be pretty clean other than that.  Let me see if I can narrow it down to just that image
Code:
version: '2.3'


services:
nextpvr:
    image: [color=#333333][size=small][font=Monaco, Consolas, Courier, monospace]nextpvr/nextpvr_amd64:latest[/font][/size][/color]
    container_name: nextpvr
    environment:
      PUID: 1028
      PGID: 100
      TZ: 'America/Denver'
      HOST_IP: "192.168.1.10"
    volumes:
      - /volume1/config/nextpvr:/config
      - /volume1/video/nextpvr/recordings:/recordings
      - /volume1/video/nextpvr/buffer:/buffer
      - /volume1/video/Video:/kodi
    ports:
      - 8866:8866
      - 8020-8030:8020-8030/udp
    devices:
      - /dev/dri:/dev/dri
    restart: unless-stopped
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:8866/login.html"]
      interval: 2m29s
      timeout: 20s
      retries: 3
      start_period: 41s
mvallevand
Online

Posting Freak

Ontario Canada
Posts: 37,340
Threads: 744
Joined: May 2006
#3
2020-06-01, 08:45 PM (This post was last modified: 2020-06-01, 08:46 PM by mvallevand.)
One thing often missing in Docker settings is

--publish 16891:16891/udp

This is for auto discovery of the server on NextPVR clients.

Also for these examples the base should be
Code:
nextpvr/nextpvr_amd64:stable
not :latest

Martin
Me123
Offline

Junior Member

USA
Posts: 4
Threads: 1
Joined: May 2020
#4
2020-06-01, 11:59 PM
Thanks to both of you for the help.
Me123
Offline

Junior Member

USA
Posts: 4
Threads: 1
Joined: May 2020
#5
2020-06-02, 12:47 AM
I have it working now, thanks for all the help.

I used this in putty

sudo docker run -d --name nextpvr --restart unless-stopped \
--volume /srv/dev-disk-by-label-Media/one/config:/config \
--volume /srv/dev-disk-by-label-Media/one/videos:/recordings \
--volume /srv/dev-disk-by-label-Media/one/buffer:/buffer \
--volume /volume1/video/Video:/kodi \
--publish 8866:8866 \
--env HOST_IP=192.168.1.73 \
--env PUID=998 \
--env PGID=100 \
--env TZ='America/Los_Angeles' \
--publish 16891:16891/udp \
--device /dev/dri:/dev/dri \
nextpvr/nextpvr_amd64Confusedtable
Ranbato
Offline

Junior Member

Utah
Posts: 48
Threads: 7
Joined: Nov 2018
#6
2020-06-02, 01:16 PM (This post was last modified: 2020-06-02, 01:26 PM by Ranbato.)
I didn't know about the publish port for 16891, I'll have to add that.

I actually run a custom image based off latest with custom builds of ccextractor, handbrakecli, and ffmpeg and I should have put in stable when I edited it.  Thanks for catching.

You're probably getting a silent error for the Kodi mapping on start so you should remove it.
Me123
Offline

Junior Member

USA
Posts: 4
Threads: 1
Joined: May 2020
#7
2020-06-02, 03:21 PM
(2020-06-02, 01:16 PM)Ranbato Wrote: I didn't know about the publish port for 16891, I'll have to add that.

I actually run a custom image based off latest with custom builds of ccextractor, handbrakecli, and ffmpeg and I should have put in stable when I edited it.  Thanks for catching.

You're probably getting a silent error for the Kodi mapping on start so you should remove it.

 I had two instances of notepad open and I am pretty sure I removed that line on the one that used, I closed one of the notepads instances after I got NextPVR working, I think I just grabbed the wrong info when I posted the code from the notepad I left open as I had not removed the Kodi volume on it yet.
I didn't notice it when I posted it in the forum that the Kodi volume was there, because I am old and have brain fade every now and then.

Everything seems to be working fine and I just need to order some new hard drives now, thanks again for the help.
« Next Oldest | Next Newest »

Users browsing this thread: 1 Guest(s)



Possibly Related Threads…
Thread Author Replies Views Last Post
  Device not showing in Synology docker irrits 1 10 10 hours ago
Last Post: mvallevand
  Docker Install Showing Version Version: 5.1.1.210328 pkscout 1 87 2021-03-30, 07:43 PM
Last Post: sub
  Alternate ports on unRAID Docker than 80:443? ainuke 2 134 2021-02-03, 05:02 PM
Last Post: ainuke
  Time is incorrect inside logs of NextPVR inside docker container janoonk 4 263 2021-01-28, 01:41 PM
Last Post: janoonk
  NPVR Synology Docker with Octopus SAT/IP finds no channels Thoschi 11 267 2021-01-23, 06:12 PM
Last Post: Thoschi
  unRaid, Docker, legacy HD Homerun - no tuners found curiousfunk 6 227 2020-12-12, 09:50 PM
Last Post: curiousfunk
  Nextpvr & Docker mexjerry 18 680 2020-11-29, 02:39 PM
Last Post: mexjerry
  Migrate recordings from Windows to Docker ewiemann 3 241 2020-11-14, 03:11 PM
Last Post: ewiemann
  AMD64 based Docker Image with Python3 pkscout 13 1,596 2020-10-26, 10:36 PM
Last Post: pkscout
  Thoughts on Building a Custom NPVR Docker Image pkscout 15 2,449 2020-10-26, 06:58 AM
Last Post: pkscout

  • View a Printable Version
  • Subscribe to this thread
Forum Jump:

© Designed by D&D, modified by NextPVR - Powered by MyBB

Linear Mode
Threaded Mode