Closed trickert76 closed 3 years ago
But the funny part is - when I comment out the network_mode: host
from nginx service, the HTTPS proxy can't reach the backend. When I comment out the ports: 8080:80
mapping it works as expected. That is strange.
Also the nginx service is configured to listen on 8080 - but the port mapping says something different (external-port:internal-port or am I wrong?)
But at the end - what is the reason for using network_mode: host in the nginx: host. In my understand of the nginx config it is still just a HTTP service that forwards requests to some other containers via HTTP. The docker-proxy should be able to handle that request - or?
yeps, that port forward is not used anyway!
As far as I can remember I used the network_mode: host
instead of a port forward due to some IPv6 issues, where quite some modifications on the host must be made for get docker with IPv6 running probably. With network_mode: host
we don't rely on docker for forwarding the ports on IPv6 as well.
I just made a commit where the port forward gets removed. should be released soon ;)
should be resolved by our latest release :)
Last night I've got an error after upgrading the BBB host. I'm not sure, but I think with docker-compose 1.27.4 there is an issue with the nginx-service definition.
and that is correct for me, because in a
network_mode: host
mode there can't be a port binding like8080:80
because the container uses the concrete network device directly without a proxy. I assume this is because now I've got docker-compose v.1.27.4 last night. But it should be fixed. Because there is port binding to an unusual port - I would expect that,network_mode: host
is wrong here. Because this would be done via https-Proxy.