A docker-compose for every Channels-related extension -- suitable for Portainer-Stacks!

Hosting Containers
#34

Though the Docker Composes posted here generally don't need to be modified, other than the env vars -- when you want to deploy multiple containers based on the same project you do. In the case of vlc-bridge-fubo, append a "2" to the container name:

For example:

version: '3.9'
services:
  vlc-bridge-fubo:
    image: registry.gitlab.com/yankees4life/vlc-bridge-fubo:${TAG}
    container_name: vlc-bridge-fubo2
    ports:
      - ${HOST_PORT}:7777 # Use the same port number the container is using, or optionally change it if the port is already in use on your host
    environment:
      - FUBO_USER=${FUBO_USER}
      - FUBO_PASS=${FUBO_PASS}
    volumes:
      - vlc-bridge-fubo:/app/Config
    restart: unless-stopped
volumes:
  vlc-bridge-fubo:
    name: ${HOST_VOLUME} # This project will store its data in /var/lib/docker/volumes/${HOST_VOLUME}. <project-name_config> is a good name choice.

  # Default Environment variables can be found below under stderr -- copy and paste into Portainer-Stacks Environment variables section in Advanced mode

And sample env vars, with HOST_PORT and HOST_VOLUME modified:

TAG=latest
HOST_PORT=7778
FUBO_USER=<yourfubousername>
FUBO_PASS=<yourfubopassword>
HOST_VOLUME=vlc-bridge-fubo_config2
#35

Also, if you could scroll this list of containers over so I can see all the way to the right and post that screenshot.

#36

Im going to try it, but can I ask you another question about a different topic?

#37

If it's a different topic, it should go in the appropriate thread. We like to keep things organized, so that people are more likely to be successful when searching for specific info related to specific topics.

#38

But what about through a personal message? because its a unique/personal issue

#39

If it's something you don't think anyone else would ever care to know -- then sure, otherwise the idea is for this to be a knowledge base. That way, "the next guy" might find his/her answers through search.

#40

ok i will message you the thing is I dont know how to post it on another topic and at the same time address it to you

#41

Using someone's username with an @ in front makes sure that the user knows the message has something they should know about. Like @bnhf or @TaliandTony @tali1 @tali2. BTW, creating multiple usernames is frowned upon.

#42

I sent it to you its under Chrome Capture for Channels

#43

I input this into portainer but this is what i got

2
21360×730 89.3 KB

here is my environment variables
FUBO_PASS=
FUBO_USER=
PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/root/.local/bin
LANG=C.UTF-8
GPG_KEY=7169605F62C751356D054A26A821E680E5FA6305
PYTHON_VERSION=3.12.5
PYTHON_PIP_VERSION=24.2
PYTHON_GET_PIP_URL=https://github.com/pypa/get-pip/raw/66d8a0f637083e2c3ddffc0cb1e65ce126afb856/public/get-pip.py
PYTHON_GET_PIP_SHA256=6fb7b781206356f45ad79efbb19322caa6c2a5ad39092d0d44d0fec94117e118
PYTHONUNBUFFERED=1

#44

You can't use 0.0.0.0 to access a locally hosted (or any) webpage, using the actual LAN IP address of the PC with the port number almost always works though.

#45

I did but still the same thing

#46

Is the container running? Also, you never posted the other Portainer screenshot I requested.

#47

yes you see i go to the ip provided and it doesnt come up here is the ip and what other screenshot are you reffering to:

1
11360×689 141 KB

#48

and here is the page when i try to load it

2
21360×730 96.5 KB

#49

You don't use that IP, you use the IP of the Docker host, which in this case is your Windows system. Figure out what that is, and then use 57143 for the port number.

#50

And, you have another problem. You changed the port number on the container side to 7778 -- which you generally do not do. The container side stays the same, and only change the host port number, when using bridge networking.

#51

I have also used that one but nothing let me know if you want a screenshot of that one too?

#52

Use the compose I posted above, exactly as I posted it, and only modify the env vars that are placed in the Environment variables section of Portainer-Stacks. You've clearly modified the compose itself.

#53

yes you were right it works now thank you brother

1
11360×725 76.3 KB