login failed with default registry
See original GitHub issueI am using docker-py (1.8.0) and trying to using login API.
If I don’t input registry='https://index.docker.io/v1/'
.
It will raise exception as following:
docker.errors.APIError: 500 Server Error: Internal Server Error ("Unexpected status code [301] :")
But I saw https://github.com/docker/docker-py/blob/81edb398ebf7ce5c7ef14aa0739de5329589aabe/docker/api/daemon.py#L52 in source code. Should work with default registry.
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (1 by maintainers)
Top Results From Across the Web
Docker login to internal registry failed with service account as ...
Issue. Failed to login to the internal registry when Openshift cluster is log in with service account. Raw.
Read more >How to Fix User Profile Cannot be Loaded in Windows 10?
Fix User Profile Server Failed to Logon via Registry Editor · Open the Registry Editor (regedit.exe) and go to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\ ......
Read more >az acr login failed · Issue #4715 · Azure/azure-cli - GitHub
az configure Welcome to the Azure CLI! This command will guide you through logging in and setting some default values.
Read more >Error Message Explained: User Profile Service Failed the Logon
This typically happens when the default profile, stored in C:\Users\Default , has incorrect permissions or is corrupt in some way. Default Profile Permissions....
Read more >docker login private registry succeeded docker run failed
Using default tag: latest Error response from daemon: manifest for registry.repo.proxy-dev-forge.asip.hst.fluxus.net/jenkins:latest not found: ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Then again, #1050 is a more future-proof solution and should fix your issue.
OK, I agree with you. Thanks.