[BUG] Dockerized Cortex behind a Proxy with custom CA won't trust online analyzers

Using Dockerized Cortex behind a Proxy with custom CA

Request Type

Bug / Question

Work Environment

Problem Description

I'm trying to setup a cortex instance on a CentOS server. I chose the dockerized version of Cortex and Analyzers.
As the instance is behind a proxy, I Setup the right parameters to use it.
With 'local' analyzers (MISP), analysis jobs work fine. When I used online analyzers, every one of them I tested so far ends up in a failure : self signed certificate in chain.

I used to have an .RPM installation and everything worked properly. I think it comes from my custom CA which isn't mounted on Cortex container.

Any advice on this ?

Steps to Reproduce

1. Setup Cortex via docker method
2. Configure a Proxy Cortex should use (custom CA for HTTPS)
3. Online analyzers won't trust the domaines they try to reach.

Possible Solutions

I think I should mount my custom CA bundle on Cortex Container. But in my case (according tot he documentation), Cortex itself runs other containers. Does that mean I should also find a way to mount my own CA bundle on those container ?

Complementary information

No screenshot for now, maybe later

Start with the Docker deployment and container setup described in the issue, focusing first on how the custom CA reaches Cortex and the analyzer containers. Reproduce the proxy-backed online-analyzer failure; the work is done when online analyzers trust the custom CA while local analyzers continue to work.