2 ms·
The reverse proxy is configured to route requests to any container that is currently running. For example, if I have a Jenkins container, as long as it is runni
by nathan-osman 9y ago
The reverse proxy is configured to route requests to any container that is currently running. For example, if I have a Jenkins container, as long as it is running, the reverse proxy will send requests to it. In this particular case, I need to proxy a remote host. In order to do that, I have a container running with the appropriate labels, the proxy sees the container running, and it proxies requests to the remote host.
- davman 9y agoI think I'm being particularly dense here, but do you mean the proxy is proxying to your tiny 1kb container? If so, what happens to the traffic? Or because the tiny container is running the proxy proxies somewhere else? i.e you're using the presence of a container with a label as configuration for the proxy?
- nathan-osman 9y agoI know, it's a bit difficult to explain and a tad confusing. No, the proxy is not sending any traffic to the container. Rather, the container, by simple virtue of being in the running state, tells the proxy to send requests to the domain specified by the label on the container.
- deleted 9y ago[deleted]
- djhworld 9y agoWhat happens if the container isn't running?
- nathan-osman 9y agoThen the proxy will not route requests to the host specified by the container's label.
- radarsat1 9y agoYou're using the running state flag of a container as an IPC mechanism?
- nathan-osman 9y agoEssentially, yes. And the labels.