Working through a proxy
Docker
If docker.mitigator.ru is accessed through a proxy, you need to configure Docker.
On systems running systemd, you need to:
Create a drop-in to the Docker service, specifying the proxy in the environment (replace the details of connecting to the proxy with the current ones):
Add proxy certificate to Docker’s trusted ones (
/path/to/proxy.crtreplace with the path to the proxy certificate):Update the description of the Docker service and restart it:
Podman
If docker.mitigator.ru is accessed through a proxy, you need to configure Podman.
Set proxy environment variables in Podman’s containers.conf (system-wide or per-user, replace the proxy connection details with the current ones):
For system-wide configuration:
For per-user configuration, use
~/.config/containers/containers.confinstead.Add proxy certificate to Podman’s trusted ones (
/path/to/proxy.crtreplace with the path to the proxy certificate):No daemon restart is needed (Podman is daemonless). If using the Podman system socket, restart it:
Collector
If Collector will communicate with the license server (ls.mitigator.ru)
through a proxy, you need to specify environment variables.
To do this, you need to create a docker-compose.override.yml file
with content like this:
If necessary, also set NO_PROXY (addresses that need to be accessed without a proxy),
you need to include .collector, localhost, 127.0.0.0/8,
10.0.0.0/8, 192.168.0.0/16 and 172.16.0.0/12 in it:
After that, you need to restart the backend service:
Do not use proxy settings in ~/.docker/config.json (Docker) or
~/.config/containers/containers.conf (Podman) configuration file for Collector containers.
If these settings are required for non-Collector containers,
specify them only for such containers.