NextPVR Forums
  • ______
  • Home
  • New Posts
  • Wiki
  • Members
  • Help
  • Search
  • Register
  • Login
  • Home
  • Wiki
  • Members
  • Help
  • Search
NextPVR Forums Public NextPVR Support Docker amd64 v
« Previous 1 … 4 5 6 7 8 9 Next »
Problem starting latest version (5.1.0.201216)

 
  • 0 Vote(s) - 0 Average
Problem starting latest version (5.1.0.201216)
dsreyn
Offline

Member

USA
Posts: 66
Threads: 13
Joined: Jan 2020
#11
2020-12-19, 06:54 PM (This post was last modified: 2020-12-19, 06:59 PM by dsreyn.)
(2020-12-19, 04:17 PM)pkscout Wrote: I'm using a Docker image built from sub's Docker image (I add Python to it), and mine is working fine with the current version. I can't imagine how or why mine would be OK and not the stock image, but you're welcome to try it:

https://hub.docker.com/r/pkscout1/nextpvr-python3

I just gave this a shot, but it didn't work either.  A difference with your version is that the startup command is "/bin/sh -c /usr/sbin/startup.sh", whereas sub's version uses "dotnet /app/NextPVRServer.dll".  However, it turns out that these new images aren't providing /bin either, so executing /bin/sh with this (pkscout1) version also fails.

Trying similar "docker cp" commands to what I mentioned previously...first, my old, working NextPVR container from a couple of months ago:

> docker cp nextpvr-nextpvr_amd641:/bin bin.641
> ls test641
bash          chgrp          fgrep    more          sh.distrib  ypdomainname
bin          chmod          findmnt  mount          sleep      zcat
bunzip2      chown          grep      mountpoint    stty        zcmp
bzcat        cp            gunzip    mv            su          zdiff
bzcmp        dash          gzexe    nisdomainname  sync        zegrep
bzdiff        date          gzip      pidof          tar        zfgrep
bzegrep      dd            hostname  ps            tempfile    zforce
bzexe        df            kill      pwd            touch      zgrep
bzfgrep      dir            ln        rbash          true        zless
bzgrep        dmesg          login    readlink      umount      zmore
bzip2        dnsdomainname  ls        rm            uname      znew
bzip2recover  domainname    lsblk    rmdir          uncompress
bzless        echo          mkdir    run-parts      vdir
bzmore        egrep          mknod    sed            wdctl
cat          false          mktemp    sh            which

So that looks pretty normal; among other things, "sh" is there.  But this fails for the two new versions, because /bin doesn't exist:

> docker cp nextpvr-nextpvr_amd642:/bin bin.642
Error: No such container:path: nextpvr-nextpvr_amd642:/bin

> docker cp pkscout1-nextpvr-python31:/bin bin.pks
Error: No such container:path: pkscout1-nextpvr-python31:/bin

So trying to execute /bin/sh in these new containers isn't going to succeed.


And here's what I get for /usr - first, the old container, then the two new ones:

> docker cp nextpvr-nextpvr_amd641:/usr usr641
> ls usr641
bin  games  include  lib  local  sbin  share  src

> docker cp nextpvr-nextpvr_amd642:/usr usr642
> ls usr642
lib  share

> docker cp pkscout1-nextpvr-python31:/usr usr-pk
> ls usr-pk
bin  include  lib  local  sbin  share

> ls -d usr641/share/dotnet
usr641/share/dotnet

> ls -d usr642/share/dotnet
ls: cannot access usr642/share/dotnet: No such file or directory

> ls -d usr-pk/share/dotnet
ls: cannot access usr-pk/share/dotnet: No such file or directory

So again, there's more stuff in the old container, and there's no /usr/share/dotnet in either of the two new ones.

It seems like there's some critical core system stuff that's assumed to exist (and had been bundled in the old container), but isn't present in these new containers.

Doug
mvallevand
Offline

Posting Freak

Ontario Canada
Posts: 52,865
Threads: 954
Joined: May 2006
#12
2020-12-19, 07:32 PM
Perhaps since Docker does incremental update one of the cached modules is corrupt. Did you try stopping your image and then completely removing it?

Martin
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 106,676
Threads: 767
Joined: Nov 2003
#13
2020-12-19, 07:55 PM
(2020-12-19, 07:32 PM)mvallevand Wrote: Perhaps since Docker does incremental update one of the cached modules is corrupt.  Did you try stopping your image and then completely removing it?

Martin
That’s what I’m thinking.
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 106,676
Threads: 767
Joined: Nov 2003
#14
2020-12-19, 07:56 PM
FYI, I’m using it on a DS418+, so pretty similar to what you’re using.
dsreyn
Offline

Member

USA
Posts: 66
Threads: 13
Joined: Jan 2020
#15
2020-12-19, 09:24 PM
I finally concluded that my Docker setup must have gotten hosed.  Weird that my existing NextPVR image from a couple months ago was still running fine, but anyway...  I deleted my Docker application and all the installed containers (but saving the NextPVR config and recordings directories) and did a fresh install.  Then the new NextPVR image installed fine.  So I don't know what happened to Docker, but - problem solved.  Sorry about the false alarm, and thanks for your patience.

Doug
sub
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 106,676
Threads: 767
Joined: Nov 2003
#16
2020-12-19, 09:41 PM
Ok - glad you got it sorted.
« Next Oldest | Next Newest »

Users browsing this thread: 1 Guest(s)

Pages (2): « Previous 1 2


Possibly Related Threads…
Thread Author Replies Views Last Post
  latest vs stable tags andrew 3 393 2025-01-16, 08:58 PM
Last Post: andrew
  Version 4 jrockow 2 596 2023-05-20, 05:18 PM
Last Post: jrockow
  Docker Install Showing Version Version: 5.1.1.210328 pkscout 3 1,770 2021-05-06, 04:12 PM
Last Post: sub
  Version 5.0.1.200209 dsreyn 17 5,154 2020-02-15, 05:39 PM
Last Post: KyleC_USA

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

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

Linear Mode
Threaded Mode