Great job on the continer for MLB tv.
Could not agree more! @crackers8199 Thank you for all your time and effort in creating and maintaining this! So awesome!! Also, Go Padres! 
Yep. Thanks for all your work. Really appreciate it.
1 Like
Yes! Amazing job! I think I only opened the mlb tv app a couple of times this year. Hopefully when in market streaming comes it can be as easily integrated!
Does this have the MLB Network channel workaround? I haven't subscribed to MLB.tv for several years but really miss the MLB Network in Channels.
1 Like
not yet. big inning was working, but i was still working on mlb network when the season ended and then just kinda gave up since the mets pissed me off.
i'll try to work on it again this week and see if i can get it working enough to do a release.
2 Likes
Indians fan here so were are in the same boat. I hope your pitching holds up next season. I don't blame you for being upset about it. I rooted for the Mets in 86.
2 Likes
I second that. I just signed up for another year and everything works great!
FYI if you haven't signed up for mlb.tv yet, here is a way to save $50 on the yearly subscription. Basically you pay $25 to join the Major League Baseball Players Alumni Association. Then you get an email with a 50% off the $150 fee. $25 + $75 = $100 instead of $150 
3 Likes
@crackers8189 The MLB docker is working great.
I'm waiting for the t-mobile offer if it should appear.
3 Likes
hi guys,
Noticed a couple of things.
- When I went to watch the San Diego Dodgers game, I could watch the Dodgers feed but I couldn't view the San Diego Feed. I'm in the L.A. market and both Times are in spring training in Arizona.
When I tried the MLB app, the San Diego feed played just fine. I'm unsure of what happened.
Looking forward to seeing how it does tomorrow when we move to another team.
Well, I'm at a loss... I am seeing a 502 Bad Gateway error no matter what I try. Not sure if this is a Ventura thing, an Apple Silicon thing or a Docker thing... (Maybe a Docker on macOS thing? Someone else seems to have the same issue... 502 bad gateway with Nginx, Colima, Docker on macos for port forwarding on 443 and 80 - Stack Overflow)
Seeing this nginx error repeating in the terminal output:
[error] 10#10: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 172.17.0.1, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "localhost:8080"
I've tried changing everything I can think of. I know macOS usually requires "host.docker.internal" in place of localhost, but it seems to have no effect.
Anyone have any thoughts?
1 Like
I'm on Apple silicon with macOS Ventura and haven't seen that error. It works for me using the IP of the Mac rather that "localhost".
Hrmm. Well, that's good to know! Thank you.
Yeah, on my old Catalina Mac mini server, I never had this issue. Just assign a static IP, use that in the config as directed & run it. Did the same thing on my new server but no luck. Maybe there's something conflicting in my setup...
This means nginx is unable to connect to the PHP backend which is supposed to be running inside the container.
Ah! Thank you for the info. That explains the
INFO exited: php-fpm (terminated by SIGSEGV; not expected)
INFO gave up: php-fpm entered FATAL state, too many start retries too quickly
errors I am getting on startup. I'm quite stumped, honestly. I set things up from scratch exactly the same way as before...
Could be the container doesn't support ARM64. I'm not sure.
1 Like
That was my thought, except nschaffner said it was working, so...
I guess it's good I still have my old Mac minis around! 
Thanks for your help!
1 Like
Yeah. But I mean, I have other AMD64 containers running under virtualization with no problems, so I'm guessing something isn't quite working with the translation layer...