Support environment variables in docker-container driver by sirlatrom · Pull Request #170 · docker/buildx (original) (raw)

Yeah, I'm aware of what the remote driver is, @tonistiigi, but it is just not clear to me yet how the environments (client env, build args, remote env, etc) "interact".

My buildkit nodes run in an environment where all the egress traffic must go through a proxy and I had a hard time getting it to work.

Perhaps something was wrong with my experiments, but AFAIR just making sure the buildkit remote nodes had, themselves, the environment variables set ({NO,HTTP,HTTPS}_PROXY and their lowercase counterparts) didn't fix the issues while pulling public images. IIRC, I had to also invoke buildx like docker buildx build --builder my_remote_builder --build-arg HTTPS_PROXY=... --build-arg HTTP_PROXY=....

Is that expected?