Issue with Docker ETF behind the proxy

[MartinTuchyna]

Dear Validator Helpdesk Team

We need to deploy containerized etf on host which is not directly connected to internet i.e. it uses forward proxy (corporate squid instance) to access internet and simultaneosly etf web UI/API would be accessed by client from internet via reverse proxy (nginx/haproxy instance). We find using etf docker container in this deployment scenario very difficult mainly because of its complicated architecture/structure (considering all the stuff running within single container i.e apache, squid, nginx).

Neverthless few months ago we came with working solution, which was working until latest etf docker image release 2022.03 (relased in September), working solution is attached to this email and is comprised of several files:

• docker-compose.yaml
• proxy.conf (overriden Apache condfiguration /etc/apache2/sites-available/proxy.conf) - the only modification here is to tell apache to use corporate forward proxy for outgoing http traffic
• squid.conf (overriden Squid configuration /etc/squid3/squid.conf) - force squid to use our corporate forward proxy (also squid) for all the outgoing http[s] traffic except traffic destined to "inspire.ec.europa.eu" domain cause that is handled by internal apache (modifications are located at the very end of file)
• config.js (overriden JS file in validator web UI app /etf/validator/js/config.js) - overide default front facing URL to let JS construct proper self referencing urls (we are behind reverse proxy)

As was said this solution was working until latest release of etf docker image 2022.03, so please check our configuraion and let us know if something has changed in latest docker image that could have "breaking" effect with regard to our configuration ...

etf.zip