Pluto TV script

Chris G · 2024-12-04T23:26:25+00:00

Here is my custom Pluto TV script for TVHeadand. It requires Streamlink and makes use of TVHeadends useful pipe options. It queries the Pluto TV API directly...

Barry

Hi Chris! Thanks for explanation.
Having a horrible time installing Alpine Linux: used the RPi Imager, the one option to RPi 4. Initial installation instructions are vague but Googling helped. First problem is the configuration not being kept; Google indicated a failing SD card so used a brand-new one. Same. Also an error about the 'network failed to load'.
Can regular Bookworm be used? (That I understand! <g>)
Thanks!

chewitt

Docker virtualises an application (and that application's runtime dependencies) instead of a machine, inside an image called a container. When the container is running Docker exposes the app binary(s) to the host machine so you can run and interact with them as if they were installed locally. Alpine Linux is commonly used for the OS runtime environment for the application inside the container as it can be configured to have a very light/minimlist configuration. You can run Alpine as the host OS for Docker, but (as with virtual machines) the whole point of Docker is you can use your normal/favourite OS, so if the RPiOS 'Bookworm' image is more familiar, install that, then install Docker, then deploy a Tvheadend container (the official one, or from linuxserver.io).

Barry

chewitt Hi chewitt! Things are starting to (slowly) make more sense -- that's the problem with being self-taught: tons of holes in the knowledge. I'm going to go back to RPi Bookworm, install Docker, then TVHeadend 'inside' Docker.

Chris G

Chewitt did a better job of explaining it than me.

You ever used a Linux live image?
IE, running Linux from a DVD/USB stick?
It's a bit like that.

Someone creates something called a Dockerfile.
It's basically a list of commands and options that tells Docker how to create the Docker image.
So that involves installing packages and or compiling stuff, their dependencies, etc.
Once the image is built, think of it as read only.
Users can "play" that image, and it will work (assuming the image is good) on any system with Docker installed (assuming the image supports the architecture).
While it's read only, you can mount local directories to directories inside the image, which can be written to.

Barry

Chris G Hi Chris! Between you and Chewitt I'll figure it out! 🙂 Have done the Ubuntu Live running from a thumbdrive ... so my Raspberry Pi is sort of equivalent to the computer/hardware, Docker is sort of the Live Image, and TVHeadend is the sort of the utilities being tested in the Live Image. (Actually was clearer before typing!)

Anyway, to this point I have created Bookworm (64-bit) on to my Raspberry Pi 4. Also installed Docker and passed the "Hello world" test. Your 'USB Live Image' explanation helped to explain the "Docker took the following steps" message.

Now to install TVHeadend - the Docker version!

Chris G

Barry Hi Chris! Between you and Chewitt I'll figure it out! 🙂 Have done the Ubuntu Live running from a thumbdrive ... so my Raspberry Pi is sort of equivalent to the computer/hardware, Docker is sort of the Live Image, and TVHeadend is the sort of the utilities being tested in the Live Image. (Actually was clearer before typing!)

No not really. Maybe my analogies suck.
Your system and host OS are what they are.
You install Docker, which is kind of like an image "player".
It lets you run Docker images.

To install TVH etc traditionally, you would need to install the required dependencies (and the correct versions).
With a good/working Docker image, it's all contained in the image, if you have docker installed, it will just work.

For instance, I have nothing installed on my host OS other than Docker and mergerfs.
All of my services are "Dockerised".
I map any required Docker volumes to a separate drive from my OS.
I use the new yaml system to configure my containers (Docker-Compose).
Because of this, I can wipe the system and be back to where I left off in minutes.
I simply install docker, map my drives, then load the yaml file.

Barry

Well, I think I'm getting there -- thanks for being patient with me!
AFAICT I have installed TVHeadend as a Docker:
docker run --name TVHeadend -p 80:8080 -d lscr.io/linuxserver/tvheadend
And running "docker ps " I get this:
barry@raspberrypi:~ $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 7cacf214d913 lscr.io/linuxserver/tvheadend:latest "/init" 9 seconds ago Up 8 seconds 9981-9982/tcp, 0.0.0.0:80->8080/tcp, :::80->8080/tcp tvheadend
Trouble is I'm not able to access TVHeadend for the initial configuration: http://localhost/tvheadend -- also tried adding ports 80, 8080, 9981, 9982. Thought maybe 'needs to be turned on'? "docker exec -it tvheadend /bin/sh" -- that gets me to the docker command line but still no web access to TVH.
Thanks again!

Chris G

That looks like the wrong ports.
Check the parameters section here: https://hub.docker.com/r/linuxserver/tvheadend

Barry

Chris G Hi Chris! I'm getting a 404-type error with a note indicating they've logged it and will look into the problem. I thin k I was on the page earlier this afternoon so will check in a bit (have to call my Mother shortly to make sure she is OK). I noted int the TVH logging it is running and looks like it is waiting for me to do the configuring -- let me in! <g> ...Also noted a 'docker0' entry in ifconfig of 172.17.0.1 -- nope, and trying to ssh to it just sits.

Chris G

Barry

404 for me too now.
A super simple way of dodging all this port mapping stuff is to simply run the container in host networking mode.
This means it automatically binds all the exposed internal image ports to the same ports on the host.
There's no problem with this until you want to run multiple images that all want to bind the same port numbers.
https://docs.docker.com/engine/network/tutorials/host/

The README is also available here: linuxserver/docker-tvheadend

Barry

Hi Chris! Just saw your reply about the 404 and will look at the new information.

Typed this off-line and maybe explains some of the access issues:

Hi Chris!
You simply have more (a lot more! <g>) experience than I do – this is my first foray into using Docker. Probably wasn’t the best first project. 🙂

Anyway I think I have have found why I can’t access. The general installation instructions I followed are from https://www.stacksimplify.com/aws-eks/docker-basics/get-docker-image-from-docker-hub-and-run-/ – I was looking for them at TVHeadend but no luck.

So at “Step-3: Run the downloaded Docker Image & Access the Application”
• Copy the docker image name from Docker Hub
<code>docker run --name app1 -p 80:8080 -d stacksimplify/dockerintro-springboot-helloworld-rest-api:1.0.0-RELEASE
http://localhost/hello </code>

So I changed that to <code> docker run --name app1 -p 80:8080 -d lscr.io/linuxserver/tvheadend:latest </code> and the ran <code> http://localhost/tvheadend </code> which didn’t work.

Found out later ‘app1’ probably should be called ‘TVHeadend’ so swapped that in, got an error message I think about duplicate ports, so found out how to remove the ‘app1’ thing, then I remembered someone mentioning issues with upper case so installed as ‘tvheadend’.

Now, I think I found the port problem: <code>
https://docs.linuxserver.io/images/docker-tvheadend/
Host vs. Bridge
If you use IPTV, SAT>IP or HDHomeRun, you need to create the container with --net=host and remove the -p flags.
Parameters
Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.
</code>

So if I decipher that my
<code> docker run --name tvheadend -p 80:8080 -d lscr.io/linuxserver/tvheadend:latest </code>
needs to be removed and re-installed substituting the -p (port) numbers forrrrrrr… haven’t a clue other than 9981 for one or the other, maybe both.

...Buy Me a Coffee button?! You’re needing a “buy me aspirin” button! <joke!>

Chris G

docker container ls will list all the containers you may have created.
You can then run docker remove <name> to remove them.

Try something like the example they give:

docker run -d \
  --name=tvheadend \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -e RUN_OPTS= `#optional` \
  -p 9981:9981 \
  -p 9982:9982 \
  -v /path/to/tvheadend/data:/config \
  -v /path/to/recordings:/recordings \
  --device /dev/dri:/dev/dri `#optional` \
  --device /dev/dvb:/dev/dvb `#optional` \
  --restart unless-stopped \
  lscr.io/linuxserver/tvheadend:latest

Just change the mounts and remove/edit the optional parameters if they are not needed.
If it helps, here is how I used to create my Docker container before I switched to the newer compose method:

docker create \
--name=TVHeadend \
--restart=unless-stopped \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Europe/London \
--network host \
-v /mnt/containers/TVHeadend:/config \
-v /mnt/storage/Downloads/Recordings:/recordings \
-v /mnt/containers/TVHeadend/startup-scripts:/custom-cont-init.d \
-v /mnt/containers/TVHeadend/startup-services:/custom-services.d \
--device /dev/dri:/dev/dri \
--device /dev/dvb:/dev/dvb \
lscr.io/linuxserver/tvheadend:latest

The startup directories are a feature from linuxserver.io.
You put scripts in these directories, and their images run them on startup... That's how I ensure Streamlink is installed.
A bit like a Linux live image, any changes made inside the container are lost on restart.
Config setting for TVH persist because we map the necessary container dirs to dirs on the host.

Barry

Chris G Hi Chris! I have not done anything with the above yet but did experiment with the suggested https://docs.docker.com/engine/network/tutorials/host/ to create a nginx server. Somehow that failed! Semi-quick summary to maybe help figure out what is going wrong.

Their 'Procedure' Step 1: docker run --rm -d --network host --name my_nginx nginx ==> gave me a SHA and what might be a Container hexadecimal.

Access Nginx by browsing to http://localhost:80/. <== The connection was reset
docker ps, docker ps -a ==> only listings TVH – no nginx

sudo netstat -tulpn | grep :80
barry@raspberrypi:~ $ sudo netstat -tulpn | grep :80
◦ tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 2117/docker-proxy
◦ tcp6 0 0 :::80 :::* LISTEN 2124/docker-proxy

They then stay to stop the container. I wanted to see what it was doing so: docker container inspect my_nginx
[]
Error: No such container: my_nginx

At this point I'm not too concerned about nginx not installing; posting should the lack of success be significant.

Some time this afternoon I'll remove the current TVHeadend I have installed and try your 'second' option -- the one with the Time Zone = London. Quick side trip to figure out how to enter mine: thinking US/Chicago or US/Central....

Barry

Well, get excited and couldn't wait until later! Removed my old tvheadend, installed the new (your second listed) TVHeadend - got some long Container ID. (Oh, it's "America/Chicago"). docker ps -- where are you?! docker start TVHeadend: there you are! http://localhost/tvheadend ==> Unable to connect. http://localhost/tvheadend:9981 ==> Unable to connect. Caught something thought: Firefox is switching my http to https -- I think that's the connection error. Will have to search my notes for how I undid that on my main computer.

Barry

Got connected finally! As noted previously, Firefox (and Chromium) kept changing my http://localhost/tvheadend (tried with and without the 9981 port) to https. At a late point I had mistyped the address and got an AI response with indicated I should be using http://localhost:9981 -- that connected!! Also can connect remotely, from another computer.

So now to configure TVHeadend and then continue with the PlutoTV Script.

Chris G

If you commit to Docker and plan to run multiple containers, I recommend running Portainer (or an alternative).
They give you a web UI to manage your Docker containers.

Barry

Hi Chris! Thanks for the tip! Remote access and making things easier are always useful!

Barry

Hi Chris! Well, I screwed up something trying to load Streamlink. 🙁 What I did --
mkdir /mnt/containers/TVHeadend/custom-cont-init.d nano /mnt/containers/TVHeadend/custom-cont-init.d/streamlink.sh ==> apk add py3-pip && pip install streamlink --break-system-packages chmod +x /mnt/containers/TVHeadend/custom-cont-init.d/streamlink.sh sudo chown -R root:root /mnt/containers
And reboot. System is now extremely sluggish: takes about a minute or so now to load the TVHeadend webpage, to get to the menu tabs; EPG never did load.

Noted the /mnt/containers belongs to root:root but the TVHeadend subdir will be owned by me (barry:barry) after a boot -- not sure when gets altered.

Just removed the custom-cont-init.d subdir; reboot, still super-sluggish. And the TVHeadend is owned by me.
(Good news: I did make a backup SD card last night!)

Chris G

Is Streamlink actually being installed?
If you get a shell into the docker container (https://docs.docker.com/reference/cli/docker/container/exec/), is Streamlink installed? Just try running Streamlink

Barry

Hi Chris!
I'll look at your link after this reply. Streamlink is not installed -- I tried the command line 'trick' yesterday. ...Actually I was thinking Streamlink would be installed via the script but apparently not.

I have 'backed up' the project a bit: to me looked like things were getting screwed up after the configuration of TVHeadend so put in the SD card. I'll look at your link for installing Streamlink.

Do have a question on some other notes: look like two different paths:
` ▪ December 4, 2024
If you are using the Linuxservers.io Docker image, you can install Streamlink as follows:
Following the instructions here: https://docs.linuxserver.io/general/container-customization/#custom-scripts
You can create a mount for custom start up scripts, e.g:

/a/local/path/startup-scripts:/custom-cont-init.d
Inside this folder, create the following file, "streamlink.sh":
apk add py3-pip && pip install streamlink --break-system-packages
This script will ensure Streamlink is installed whenever the image is updated.`
I interpret that as something like "/home/barry/start-up-scripts:/custom-cont-init.d/streamlink.sh". The colon is confusing me, plus the referenced

https://docs.linuxserver.io/general/container-customization/#custom-scripts
Custom Scripts
The first part of this update is the support for a user's custom scripts to run at startup. In every container, simply create a new folder located at /custom-cont-init.d and add any scripts you want.

I'm interpreting as /mnt/containers/TVHeadend/custom-cont-init.d/streamlink.sh

The latter is what I used yesterday, but LIS didn't install Streamlink.

« Previous Page Next Page »