-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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-compose build --pull
on Mac fails with no basic auth credentials
#6713
Comments
@rca did you do a |
Indeed. Simply downgrading the packages works, upgrading them back to the new versions breaks. |
@rca, thanks for the answer. Does a simple Are you using any credential helpers? Please could you post the content of |
I have tried removing the image locally and pulling. The My Docker config:
|
I noticed the
The
Per my initial post, this does work with |
Thanks @rca. You are using the Your theory about @ulyssessouza do you know what the situation is wrt bumping to |
We should be able to bump |
Awesome, thank you @ulyssessouza! 🙌🏽 |
I had the same issue in IOS. For uninstall i used AppCleaner. |
We are experiencing this issue with the latest version of (2.1.0.0) Build 36874 Specifically we can successfully pull via docker pull, but when a private image is used as a FROM
I am logged in via docker login, as i can successfully pull with:
For more context, this error has existed in docker edge for months. Funnily enough after upgrading to the most recent version of docker edge, it is not affected by this bug. |
We're experiencing this, too, using the same versions as @fonged. I'm wondering why this issue is tagged as a My team is having to downgrade to v2.0.0.3 to work around this :( |
Hi all, I'm experiencing the same issue. I'm not able to pull image from private repositories (AWS ECR in my case) using docker-compose but I'm able to pull same images using docker. Thanks |
Looks like the last reproductions are related to #6517 (comment) |
@ulyssessouza this is not a docker-compose problem. I've isolated it to a commit in Also have a PR open with a candidate fix which works for me locally: docker/docker-py#2401. Not sure if it's the correct fix, but at least should hopefully shed light in the right area. |
Experiencing the same... |
Just found that we are experiencing this as well. My forehead is sore from banging it on my desk. |
Bump! My organization has this issue as well. |
docker/docker-py#2401 has been merged, so we just need a release of docker-py to get this fixed |
https://github.com/docker/docker-py/releases/tag/4.1.0 was released 11 days ago |
Description of the issue
When installing
docker
anddocker-compose
in a virtual environment, the current versions that are installed are:When building a project that is pulling the
FROM
image from a private repo I get the following error:Context information (for bug reports)
Output of
docker-compose version
Output of
docker version
Output of
docker-compose config
(Make sure to add the relevant
-f
and other flags)Steps to reproduce the issue
Observed result
Expected result
When configuring the virtual environment with the following, build succeeds:
Stacktrace / full error message
Additional information
pip install
in a pipenv-created virtual environmentThe text was updated successfully, but these errors were encountered: