agreed 100% that they should do this, but until they do our hands are tied. we cannot and will not support attempting to circumvent the blackout rules.
1 Like
So question for you. I couldn't do what tgcon was suggesting with Windows Powershell but I did figure out how to open inbound and outbound port for 8092. I'm seeing more "activity" in the log section of Docker Desktop but no populated channel info...
1 Like
Here are new log files from this command: docker exec -it channels-baseball cat /var/www/html/storage/logs/laravel.log
your mlb credentials are invalid. it says it right in that first error msg.
I've been following this thread and having issues as well. Windows install using Docker Desktop. The container is loaded and running but the m3u and epg files are not being created. Pluto is working fine on port 8080. I tried running MLB on port 8080 with the same result, the m3u and epg files were not created. Attached is a screenshot of the docker run command. At the end it shows the 404/file not found response when I used Docker to open the container in a browser. Any help is appreciated.
attempting to go to the root is going to show you the not found error because that page doesn't exist. there is nothing living at the root.
/epg and /m3u are the only two links that mean anything (there are other routes that the m3u will link to, but for the most part those are the only two you need to worry about). what does the log say if you try to navigate to /epg or /m3u?
Assuming you mean Channels log
2021/05/24 19:16:09.481849 [ERR] Unexpected m3u response: 404 Not Found
no, i mean use a browser and try to go to those two URLs. you should see the xml guide and the m3u playlist...if you can't see them in a browser, channels can't either.
looks like that was my issue. thanks.
1 Like
Awesome indeed! Now to set Quadstream so I can have 4 games up. Thanks again.
1 Like
just be careful, if you're using the streams direct from the docker container your hardware needs to support it. I couldn't get more than three 720p60 streams running at the same time on the Chromecast google tv without them all choking...
- I built and installed a fresh Rasberry Pi, got it working on USB hard drive
- I installed Channels, got it working.
- I installed docker the wrong way and then the right way. Seems to be working, my first exposure so learning a lot there.
- I build the docker-compose.yml and edited it
I edited the bits I needed to change in the docker run command
When I run them I get:
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm/v7) and no specific platform was requested
standard_init_linux.go:228: exec user process caused: exec format error
the "docker images" command shows
REPOSITORY TAG IMAGE ID CREATED SIZE
matty8199/channels-baseball 1.2.2 4d26dc3a9c6b 7 days ago 183MB
So it seems something is there, not running?
I build the custom m3u in Channels, no errors there but no channel lineups or anything else shows up there.
What did I miss? and, thanks!
Read some articles by randomly searching on the error, this may have something to do with the newer fresher release of docker. I explicitly specified --platform linux/arm/v7 in a new docker run file, and error changed to:
Status: Downloaded newer image for matty8199/channels-baseball:1.2.2
docker: Error response from daemon: image with reference matty8199/channels-baseball:1.2.2 was found but does not match the specified platform: wanted linux/arm/v7, actual: linux/amd64.
See 'docker run --help'.
And it may be that with all the thrashing, ripping and and rescripting that I've done today, that I have no cotainers anymore:
marc@dvr-green:~ $ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
matty8199/channels-baseball 1.2.2 4d26dc3a9c6b 7 days ago 183MB
marc@dvr-green:~ $ docker container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
marc@dvr-green:~ $
I'm no docker expert but it sounds like the host is ARM and it won't run a amd64 container. You can't change the container build to ARM. You might want to install docker on a non ARM host.
Running into some streaming issues on my dedicated 10th gen i3 mini box. I can get streams up and running per instructions, but Iām getting the following message popping up after about 7-10 minutes of a stream.
When I restart docker, things are fine and I can stream again.
Any thoughts as to why?
1 Like
Any errors in the docker log? When this error appears are you still access the DVR web UI? If so, any errors in the log there?