Use https-portal as a proxy for host running directly on the host outside docker

[damascene]

Is it possible to have a domain that is connected to a port in the host instead of a docker container?

Example:

https-portal:
  # ...
  environment:
    DOMAINS: 'wordpress.example.com -> http://wordpress:80, another_domain.example.com -> http://127.0.0.1:8118'

So the second domain would be an app running on the host machine. I saw some suggestions to use host.docker.internal but it didn't work in my case.

Any suggestions please?

[SteveLTN]

The hostname host.docker.internal might depend on your Docker environment. (I think it's only available on Docker Desktop app for Mac and Windows). A quick search led me to this article. But I haven't tried myself.

In general, as long as the application inside the Docker container (in this case, Nginx in HTTPS-PORTAL) can access the hostname, it will work just fine.
I would tap into a docker container and see if I can curl the app running on host machine.

[damascene]

Thank you for responding. I'm using the Host’s Docker IP Address as in the Method 2 in the article. It's working for now.

service1.mywebsite.com -> http://172.17.0.1:8080

The interface is named docker0 in my host. I heard sometimes the IP could change but it's running fine for testing.

Thank you

[delfuego]

For future reference, I think that on Linux, the hostname dockerhost resolves to the IP address of the Docker host; at least I've found that to be true, and then used it in my DOMAINS definitions.