I'm getting guide data with the Tubi docker.
I swear Docker hates me, I run the command and everything installs corrently and then nothing. I go to 127.0.0.1:7777 and it won't connect. I've even did a full unintall of docker and still same thing. 
If you used the Portainer Stack:
What did you put down for the port? 7778 like in the example?
If you used the command line to start the docker, what port number did you choose?
I'm using the 7777 as the port.
docker run -d --restart unless-stopped --network=host -e TUBI_PORT=7777 --name tubi-for-channels ghcr.io/jgomez177/tubi-for-channels
OK. How did you start running the docker?
1 Like
yup "2024-02-23 16:12:08 ⇨ http server started on [::]:7777"
I get the same thing unable to connect, I removed the container and via CMD ran the command and started it "2024-02-23 16:13:28 ⇨ http server started on [::]:7777"
still unable to connect.
So i'm on the same computer so everything is local, but when I use the same IP address that my compter is..same deal unable to connect.
Can't find this on DockerHub. Will you be putting it up there soon? I want to add this to my Synolgy NAS and it's easiest from DockerHub. Thanks for the great work!
1 Like
Thinking out loud: could there be another docker that uses the same port 7777 so you would have a port conflict?
I believe gomez had Plex using 7777
1 Like
Trying to manage more than a few Docker containers via the command line can be frustrating, and error-prone. At my count today there are at least 18 container-based projects that one might want to run with Channels.
I'd highly suggest you install Portainer, either from the command line, or it's available as an extension for the various flavors of Docker Desktop. This should help you get a handle on what's happening with your Docker environment. It does a great job of turning chaos to order. 
Here's how you'd spin up Portainer from the command line:
docker run -d -p 8000:8000 -p 9000:9000 -p 9443:9443 --name portainer \
--restart=always \
-v /var/run/docker.sock:/var/run/docker.sock \
-v portainer_data:/data \
cr.portainer.io/portainer/portainer-ce:latest
After that, navigate to http://<docker-host>:9000 or https://<docker-host>:9443 to set your username and password. From there, the world of containers is yours to command:
I know squat about using docker compose ... but I do have portainer installed. Is there any instructions you know I can read to get started. ?
In Portainer-Stacks there's an editor, paste your docker-compose in there. After that go to the environment variables section just below that, and click on "Advanced mode" where you'll be able to paste in any environment variables. Modify the variables to suit your setup, either in Advanced or Simple mode. When you have those two sections to your satisfaction, click "Update the stack".
Go to Portainer-Containers to see what's running -- on what ports. Portainer-Images will let you delete outdated images you have hanging around. To pull an updated container, stop its stack, and go back into the editor. Make any changes (if needed), and click "Update the stack" followed by clicking the re-pull and re-deploy slider. That's about it!
1 Like
Do you have multiple containers? is another using port 7777 already - all of my containers use 7777 by default. Could probably change defaults on all to avoid conflicts but for now they all start by default that way...Need to remap that port to an unused one with either
- -p option
or - -e TUBI_PORT and network=host option
Thanks easy enough ... I am sure others will also find this useful ... going to start with OliveTin
I am ok I use 7778 for TUBI.
Actually I’m moving away from Docker Hub in preference for GitHub as it allows me to better manage the source code plus can create the containers for both linux amd64 as well as arm64