Right, but I've switched to my phone to work on it, so, yea, that's not a terminal into my Shield, I'm running it on my phone now.
What does
docker logs --tail 32 9c43f5642bb5
show?
Considering you're running Docker in a limited chroot on a modified Linux kernel without a proper full userland and an opaque network configuration, I doubt you're going to have much success.
If this is your only purpose, then you're better of with a Pi Zero-W or similar host your container. (Or, since it'd be a single purpose device, just run it natively via Node.js and ditch the massive overhead that Docker adds to the situation.)
It shows no such container
I also had to remove the container for it to run again after restarting.
True on all that, I just like to tinker with stuff, or no reason why it couldn't ask be done on the shield, and here it is running, just not working. I don't even watch the PlutoTV channels, I'm just playing with my toys right now.
Your Container ID changed. Try
docker logs --tail 32 pluto-for-channels
1 Like
I saw that and changed it to the correct one:
Looks like it works. Just can't get anything to come up. I'll keep playing with it I guess.
Networking with docker is always a hassle, so not surprising Android OS is not setup correctly for it.
Guess it was worth a shot.
1 Like
Pluto for Channels was updated to v1.1.0
This release adds the ability to generate multiple feeds with their own unique IDs.
By using a comma separated list of words without spaces, you can generate multiple feeds.
docker run -d --restart unless-stopped --name pluto-for-channels -p 8080:80 -e VERSIONS=Mom,Dog jonmaddox/pluto-for-channels
6 Likes
Works as designed Thank You....
I am confused on the functionality here? If you can't edit the m3u list why do you need multiple feeds?
Maybe you want to host it for other people.
This like something interesting. Is there an idiots guide for how to setup and configure for Channels DVR running on Synology NAS?
1 Like
Sorry basic question, what is the easiest way to keep the repo updated
I've been having issues with the PursuitUp Pluto channel for the past couple days. The channel will only play for a few seconds and then stop. Looking at the log files, it appears the "[M3U]" line is not being logged after changing to the PursuitUp channel like it does for other channels. It just starts the connection and then stops the connect a few seconds later. I've install the latest version of the PlutoTV Docker setup but it's still doing the same thing. Anyone have any suggestions? Here's the log info:
2021/01/25 12:31:47.233814 [TNR] Opened connection to M3U-PlutoTV for ch9193 PursuitUP [transcode=none]
2021/01/25 12:31:53.337685 [TNR] Closed connection to M3U-PlutoTV for ch9193 PursuitUP
2021/01/25 12:35:55.582424 [TNR] Opened connection to M3U-PlutoTV for ch9193 PursuitUP [transcode=none]
2021/01/25 12:36:04.681019 [TNR] Closed connection to M3U-PlutoTV for ch9193 PursuitUP
2021/01/25 12:40:04.186748 [M3U] stream timestamps: pluto-tv-backcountry: start_at=2021-01-25T12:40:02-06:00 current_at=2021-01-25T12:40:12-06:00 end_at=2021-01-25T12:40:22-06:00
2021/01/25 12:40:04.186787 [TNR] Opened connection to M3U-PlutoTV for ch9192 Pluto TV Backcountry [transcode=none]
2021/01/25 12:40:22.194432 [TNR] Closed connection to M3U-PlutoTV for ch9192 Pluto TV Backcountry
2021/01/25 12:40:29.678766 [TNR] Opened connection to M3U-PlutoTV for ch9193 PursuitUP [transcode=none]
2021/01/25 12:40:35.828057 [TNR] Closed connection to M3U-PlutoTV for ch9193 PursuitUP
It looks like the Pluto TV app is having a hard time playing that channel as well. Must be something on their end.
1 Like
Do you have a recommendation on a beginner's tutorial of how to do this? I found a couple on Youtube, but I'm having trouble connecting the basic instructions of setting up nodejs and how to get the code from github to run. (Sorry, I'm not a programmer, but I want to learn this.)
1 Like
I'm having some challenges adding Pluto and was hoping to get some assistance. Here's what I've done so far.
- installed docker on a pi using standard process and confirmed it's working with 'docker run hello-world'
- ran the docker setup command from the git: 'docker run -d --restart unless-stopped --name pluto-for-channels -p 8080:80 jonmaddox/pluto-for-channels'
- went to the local pi url:8080 and confirm that I see the "Pluto for Channels" landing page, however, I get a 404 error when I click the m3u or the epg links on that page.
- I tried rebooting everything, and confirmed the docker reload using "docker ps" which gives this output
c0113c0ad502 jonmaddox/pluto-for-channels "/usr/src/app/entryp…" 38 minutes ago Up 24 minutes 0.0.0.0:8080->80/tcp pluto-for-channels
- so next I went to the docker logs and I see this error when the 404 is happening.
2021/02/02 19:26:26 [error] 11#11: *1 open() "/usr/share/nginx/html/epg.xml" failed (2: No such file or directory), client: , server: localhost, request: "GET /epg.xml HTTP/1.1", host: ":8080", referrer: "http://:8080/"
I'm not 100% sure what I should to do to correct this since I'm not 100% sure what's happening under the hood here. Any suggestions?
Edit: I also see the following in the logs if it's helpful
[INFO] Grabbing EPG...
http://api.pluto.tv/v2/channels?start=2021-02-02%2020%3A00%3A00.000%2B0000&stop=2021-02-03%2002%3A00%3A00.000%2B0000
http://api.pluto.tv/v2/channels?start=2021-02-03%2002%3A00%3A00.000%2B0000&stop=2021-02-03%2008%3A00%3A00.000%2B0000
http://api.pluto.tv/v2/channels?start=2021-02-03%2008%3A00%3A00.000%2B0000&stop=2021-02-03%2014%3A00%3A00.000%2B0000
http://api.pluto.tv/v2/channels?start=2021-02-03%2014%3A00%3A00.000%2B0000&stop=2021-02-03%2020%3A00%3A00.000%2B0000
undefined:1
undefined
^
SyntaxError: Unexpected token u in JSON at position 0
at JSON.parse ()
at Request._callback (/usr/src/app/index.js:70:24)
at self.callback (/usr/src/app/node_modules/request/request.js:185:22)
at Request.emit (events.js:210:5)
at Request.onRequestError (/usr/src/app/node_modules/request/request.js:877:8)
at ClientRequest.emit (events.js:210:5)
at Socket.socketErrorListener (_http_client.js:407:9)
at Socket.emit (events.js:210:5)
at emitErrorNT (internal/streams/destroy.js:84:8)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
mv: can't rename '*playlist.m3u': No such file or directory
mv: can't rename '*epg.xml': No such file or directory
Last ran: Tue Feb 2 20:49:20 UTC 2021
You might want to blow it up and start over. It was pretty straightforward when I set it up and seems that is the expected result. Seems like something went sideways in there somewhere.
It's a good thought. I just tried that and got the same results again unfortunately. Is there anything else that I can provide which might help with others helping me?