Avoid http_proxy env from the system host injected to mailcow containers about mailcow-dockerized HOT 2 OPEN

Maybe is a docker error?
https://forums.docker.com/t/prevent-docker-from-passing-proxy-to-container/92718

from mailcow-dockerized.

Seems like some things will never change... For example, the Sun will always rise in the east and set in the west. The Moon will always wax and wane. And Docker doesn't know what to do with proxies. But if we take a closer look you made it pretty sure to use that proxy:

1. The proxy variables will be passed to the container's env. because of the content of your ~/.docker/config.json
   There is no need for that if you don't want the running container itself to use that forward proxy.

2. If you want to use the forward proxy for pulling the container images, the systemd service override should be enough. If I were you I would modify that dirty script somehow like:

sudo EDITOR=tee systemctl edit docker.service << 'EOF'
[Service]
Environment="HTTP_PROXY=http://myproxy:8080"
Environment="HTTPS_PROXY=http://myproxy:8080"
Environment="NO_PROXY=192.168.0.0/16,172.16.0.0/16,127.0.0.0/8,10.0.0.0/8,172.22.1.0/24"
EOF

This way you don't need to create the drop-in folder and neither reload systemd. (But it's still... not so nice)
If you don't believe me, check it by yourself with sg. like
docker run --rm -it alpine:latest env
with and without your configs.
docs: https://docs.docker.com/network/proxy/

IMHO it's not a mailcow related issue and I would close it. But don't give up and I wish good luck to you!

from mailcow-dockerized.