Do I need to map the ports?

[wsw70]

As I am investigating my problems with TSDproxy , I noticed that the containers that "work" all have their ports mapped.
The ones that do not, do not have the mapping.

Going from

services:
  nginx:
    image: nginx:latest
    restart: unless-stopped
    ports:
      - 8888:80
    labels:
      - tsdproxy.enable=true
      - tsdproxy.container_port=80
networks: {}

to (ports: removed)

services:
  nginx:
    image: nginx:latest
    restart: unless-stopped
    ports:
      - 8888:80
    labels:
      - tsdproxy.enable=true
      - tsdproxy.container_port=80
networks: {}

breaks the connectivity.

Since TSDproxy is discussion with the containers at docker level (and therefore on the docker network) I do not understand why the mapping would be needed.

Note: I tried v1 and v2, with -for v2- tsdproxy.port: "443/https:80/http" (I also tried tsdproxy.port.1: "443/https:80/http" ( with .1))

[wsw70]

This is really weird. Here is an example from a container (Gitea) that exposes the service on 3000:

  gitea:
    image: gitea/gitea:latest
    labels:
      - traefik.enable=true
      - traefik.http.routers.gitea.rule=Host(`gitea.XXX`)
      - traefik.http.services.gitea.loadbalancer.server.port=3000
      - tsdproxy.enable=true
      - tsdproxy.port=443/https:3000/http
    ports:
      - 52001:3000
    restart: unless-stopped
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - gitea:/data

The above works. If I remove the port binding, it stops to work, despite 52001 not being referenced in TSDProxy

[MischaBoender]

I ran into the same issue. If you don't specify the "ports" section in your compose file TSDProxy will give an error that the container has no ports. Technically it should not be necessary to expose ports on the host for a proxy to work, as it can directly connect to the container. I would expect TSDProxy to be similar to, for example, Treafik, where you configure the port the container uses only in a label and the proxy connects to it within the Docker network.

ERR error generating target error="no port found in container" container=/echo docker=local module=proxymanager port=tsdproxy.port.1
WRN No ports configured module=proxymanager proxyname=echo

[wsw70]

What I find surprising is that this is not addressed in the docs, and all the pictures hint at accessing the containers internally (there is one place in the docs where it is somehow mentioned)

Then it is just the act of exposing ports that counts, not the ports themselves. I expose the ports of the apps I need on some random very high port and never use it anywhere

It looks like a design choice: "having ports in the config is a prereq for tsdproxy to work". Really surprising.

[MischaBoender]

What might work (haven't tested) is "exposing" the ports only on 127.0.0.1.

ports:
  - 127.0.0.1:3000:3000

[wsw70]

What might work (haven't tested) is "exposing" the ports only on 127.0.0.1.

ports:
  - 127.0.0.1:3000:3000

Good idea, but it does not work. I added 127.0.0.10: to my exposed ports on a service but the proxy does not work then anymore.

[wsw70]

@almeidapaulopt - would you have any input or clarification?