Lost with Docker Port Forwarding

Docker Desktop
,
1

I would say that I am new to Docker, but I have made several attempts over the years…none of which have been successful. Here I am however lol.

I have Docker Desktop version 4.32.0 (157355) (macOS, Intel i5, Mac mini). I issued a pull command via Terminal of docker pull fyb3roptik/threadfin and can very nearly get it running. Apparently, my issue is Docker port forwarding. I tried and failed to accomplish that earlier, removed any evidence of those attempts, and I am here to try it with some help.

I have run the container via Docker Desktop and the log presents me with URL for the web interface. Of course I cannot access this web interface via http://172.17.0.2:34400/web/ and my limited understanding of why is this issue of Docker port forwarding.

Earlier I found and used these instructions, but apparently made a mistake along the way and deleted all of it for a fresh start:

Step 1: Identify the Container Port

For port forwarding, the first step is determining which container port you wish to expose. This may be accomplished by viewing the Docker container through the following command:

docker inspect <container_name_or_id>

This command will return a full JSON representation of the container setup. Check for the “ExposedPorts” section.

Step 2: Choose a host port

Once the container port has been identified, you must select a host port to which it will be mapped. A host port on the Docker host is a port that receives traffic from the container port. On the Docker host, you can select any accessible port. Port 8080 will be used in this example.

Step 3: Map the ports

The “docker run” command is then used for mapping the container port to the host port.

Following is the syntax of the command:

docker run -p <host_port>:<container_port> <image_name>

Now the host port 8080 will be mapped to container port 80 for the “nginx” image:

docker run -p 8080:80 nginx

This command will launch a new container with the “nginx” image and map host port 8080 to container port 80.

Step 4: Test the connection

After mapping the ports, you can test the connection in a web browser by going to the Docker host’s IP address and port 8080. If all is in order, you will see the standard Nginx welcome page.

I feel that if I could simply access the web interface, I would be fine from there. I am not sure what else you might need that would be helpful, but I would be happy to provide anything.

2024-07-11 13:44:04 
2024-07-11 13:44:04 2024/07/11 17:44:04 [Threadfin] [WARNING] Don't run this as Root!
2024-07-11 13:44:04 2024/07/11 17:44:04 [Threadfin] Version:                1.1 Build: 16
2024-07-11 13:44:04 2024/07/11 17:44:04 [Threadfin] Database Version:       0.5.0
2024-07-11 13:44:04 2024/07/11 17:44:04 [Threadfin] System IP Addresses:    IPv4: 2 | IPv6: 1
2024-07-11 13:44:04 2024/07/11 17:44:04 [Threadfin] Hostname:               b9cb9a6ac661
2024-07-11 13:44:04 2024/07/11 17:44:04 [Threadfin] System Folder:          /home/threadfin/conf/
2024-07-11 13:44:04 2024/07/11 17:44:04 [Threadfin] Load Settings:          /home/threadfin/conf/settings.json
2024-07-11 13:44:05 2024/07/11 17:44:05 [Threadfin] Temporary Folder:       /tmp/threadfin/2024-07-D3ZV-XLYV4Q/
2024-07-11 13:44:05 2024/07/11 17:44:05 [Threadfin] GitHub:                 https://github.com/Threadfin
2024-07-11 13:44:05 2024/07/11 17:44:05 [Threadfin] Git Branch:             Main [Threadfin]
2024-07-11 13:44:05 2024/07/11 17:44:05 SOURCE:  PMS
2024-07-11 13:44:05 2024/07/11 17:44:05 [Threadfin] SSDP / DLNA:            true
2024-07-11 13:44:05 2024/07/11 17:44:05 [Threadfin] [WARNING] Updates are disabled in the settings
2024-07-11 13:44:05 2024/07/11 17:44:05 [Threadfin] UUID:                   2024-07-D3ZV-XLYV4Q
2024-07-11 13:44:05 2024/07/11 17:44:05 [Threadfin] Tuner (Plex / Emby):    1
2024-07-11 13:44:05 2024/07/11 17:44:05 [Threadfin] EPG Source:             PMS
2024-07-11 13:44:05 2024/07/11 17:44:05 [Threadfin] Plex Channel Limit:     480
2024-07-11 13:44:05 2024/07/11 17:44:05 [Threadfin] Unfiltered Chan. Limit: 480
2024-07-11 13:44:05 2024/07/11 17:44:05 [Threadfin] All streams:            0
2024-07-11 13:44:05 2024/07/11 17:44:05 [Threadfin] Active streams:         0
2024-07-11 13:44:05 2024/07/11 17:44:05 [Threadfin] Filter:                 0
2024-07-11 13:44:05 2024/07/11 17:44:05 [Threadfin] DVR IP:                 172.17.0.2:34400
2024-07-11 13:44:05 2024/07/11 17:44:05 [Threadfin] Web Interface:          http://172.17.0.2:34400/web/ | Threadfin is also available via the other 2 IP's.```
2

Be careful with shard links. Your post almost looked like a spam to me when I saw the link on the text “IP address”, but it was quoted from the purevpn website.

If you start with these kind of blogposts I understand if you are lost. Let me share my template for learning the basics

Recommended links to learn the basics and concepts:

What you saw in the container log was what the process in the container new about. It will not know what your host IP is. You have to use your host IP or “localhost” or 127.0.0.1 with the host port. You can’t access a container port when using Docker Desktop.