-
Notifications
You must be signed in to change notification settings - Fork 482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker Desktop proxy not being recognized when doing a build. #1979
Comments
This looks related to #1487. |
Hi @crazy-max! Thanks for looking at this issue. You are right, it does look related to the issue discussed in #1487 . I am not overly familiar with what Docker Desktop does when we set the proxy information in the GUI. Is it supposed to set the proxy information in I suppose once #1487 is resolved, the Docker Desktop client would then be in a better position to move forward with what to do but I must leave it up to the developers to decide. If everyone feels this issue is another facet of the same problem and want to close, I am OK with that. If it's an extension of #1487 and requires more work to be done when #1487 is completed, and this issue needs to remain open, I am ok with that too. In either case, I just want to give a shout out to the development teams of buildx and Docker Desktop. You guys are awesome and the work you do is greatly appreciated! |
any update? |
1 similar comment
any update? |
any update? I cannot pull images on M1 MacBook,using OrbStack |
Just leaving an update for those who asked... As of version 4.34.2 on Mac, I am no longer having a build issue. Not sure if this is because of the version of DD I'm using, or because we have changed our internal proxy servers but things have been good for me for some time. I run without any environment variables set, no proxy server set in DD and I am able to build both on and off the proxy. |
I modified the buildkitd.toml and set "[registry."docker.io"]",it works well |
Contributing guidelines
I've found a bug and checked that ...
Description
Running the Docker build command will work fine when OFF the VPN and I disable the Proxy settings in Docker Desktop.
Expected behaviour
When we do the command:
$ docker build -t foo:latest -f Dockerfile_bad .
While on VPN and the Proxy information set in Docker Desktop, we expect the images in the FROM command to come down, just like they would when NOT on VPN.
Actual behaviour
When the command
$ docker build -t foo:latest -f Dockerfile_bad .
is run while on VPN and the proxy settings made in Docker Desktop, the build fails. This only happens when we have a FROM command that uses an image from docker.com. If we use an image from another repository, like IBM's registry (registry.access.redhat.com/ubi8/ubi:latest), the build will work because it does not go to docker.io to authenticate the user.
Once the image comes down, the "docker build" command will work fine because the image is in the build cache. If we use "docker compose build", the command works fine. It only fails during a "docker build" of a Dockerfile that uses an image from docker.com, while on VPN, the terminal window does not have the HTTP_PROXY or HTTPS_PROXY variables set and the image is not in the build cache.
Buildx version
github.com/docker/buildx v0.11.0 687feca
Docker info
Builders list
Configuration
dockerfile FROM alpine
console docker builder prune WARNING! This will remove all dangling build cache. Are you sure you want to continue? [y/N] y docker build -t foo:latest -f Dockerfile_bad .
Build logs
Additional info
Originally submitted as a ticket to Docker Desktop crew (Case #00069851).
Solution is to set the HTTP_PROXY, HTTPS_PROXY and NO_PROXY environment variables in the terminal before running the build. The proxy settings set in Docker Desktop are not used when connecting to docker.io but ARE used when connecting to other repositories like IBM's repository for UBI.
The text was updated successfully, but these errors were encountered: