App Developer Feedback

0
Dear community,   We've recently identified a behavior related to a specific Docker Compose network configuration, and we're seeking your urgent feedback to understand the situation better.   To help us investigate this issue quickly, we would be grateful if you could let us know if you are currently using, or are aware of, an application with the following Docker Compose setup: A network named "proxy-redirect" is declared in the networks section of your docker-compose.yml file. However, a container or service that exposes a UI via the reverse proxy of the IE device within that same Docker Compose setup is NOT explicitly connected to this "proxy-redirect" network.   Thank you very much for your prompt support and collaboration!   Best regards, Tim
asked
1 answers
0

Hi Tim,

We don't use that exact configuration, but I would strongly recommend also checking for deployments where:

  • The proxy-redirect network is defined as an external network.
  • Services are connected indirectly through multiple compose files.
  • Reverse-proxy connectivity is added dynamically by deployment scripts rather than being declared in docker-compose.yml.

In some environments, the effective network connectivity differs from what is visible in the main compose file, so searching only for explicitly attached services may miss affected installations.

It may also help to clarify:

  • Which IE version(s) are affected.
  • Whether this is a functional issue, security issue, or upcoming breaking change.
  • Whether the concern applies only to UI services behind the reverse proxy or to all containers.

Providing those details might help the community identify impacted setups more quickly.

Hope this helps gather additional feedback from users with more complex Docker Compose deployments.


answered