Docker swarm stack with http_proxy #41669
Labels
area/stack
kind/bug
Bugs are bugs. The cause may or may not be known at triage time so debugging may be needed.
version/19.03
Description
When deploying docker stacks to a docker swarm the http_proxy values in the config.json are not injected as environment variables into the containers created by the stack.
It appears that when the swarm creates containers as part of a stack it is either ignoring or cant access to the
.docker/config.json
file in the user folder.There are only 2 users that exist on this machine and i have put a file in the directories of both
Steps to reproduce the issue:
.docker/config.json
docker run alpine env
Describe the results you received:
No proxy environment variables are created inside containers created by swarm.
Describe the results you expected:
http_proxy environment variables should be populated inside each container created by the stack
Additional information you deem important (e.g. issue happens only occasionally):
I have followed the instructions in both these places
https://docs.docker.com/network/proxy/
https://docs.docker.com/config/daemon/systemd/#httphttps-proxy
I can see the proxy values in
docker info
on the hostOutput of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: