Credentials do not work for "docker login" - docker

Copy/pasting my username and password into the Docker Hub website works fine.
The password is long, but does not contain shell-breaking symbols.
Copy/pasting those same credentials into command-line docker login results in an incorrect username or password error. I have tried passing the credentials interactively (both copy/pasting and typing) and through command line args, same result:
# INTERACTIVE
$ docker login
Login with your Docker ID to push and pull images from Docker Hub. If you don't have a Docker ID, head over to https://hub.docker.com to create one.
Username: my#email.com
Password: <REDACTED>
Error response from daemon: Get https://registry-1.docker.io/v2/: unauthorized: incorrect username or password
# COMMAND LINE
$ docker login -u my#email.com -p <REDACTED>
Error response from daemon: Get https://registry-1.docker.io/v2/: unauthorized: incorrect username or password

#mustaccio was correct.
The Docker Hub website allows you to login with either your username OR your email, and the website does not require a case-correct username.
docker login DOES require a case-correct username, and DOES NOT work with your email address.
When I signed up I chose a camel-cased username e.g.:
MyUsername
Docker forces this username to all lower case in practice. When you log in, you'll see your correct username in the upper right-hand corner of the website. In this example:
myusername
The website allows you to login with MyUsername or myusername.
docker login only allows myusername.

Same issue happens if you didn't logout and if you have put EMAIL address for login.
docker logout
docker login
DONOT PUT EMAIL ADDRESS, instead ENTER USERNAME

I used a password generator that put special characters in my password, I was able to login in my browser but not through the cli. I changed it to just letters and numbers and it worked.

Try this:
sudo chmod 666 /var/run/docker.sock
sudo docker login

I solved the problem by this way.
Go to https://hub.docker.com/settings/security and create a new token in my account.
To login use
docker login command
And type:
myusername in lowercase and
token (instead of password)

If You are using git bash on Windows then use following command:
winpty docker login --username <yourusername>
It will prompt for password. Enter your password. Message "Login Succeeded" displayed.
"yourusername" you can get on right top corner when logged in docker official site.
With your email it is not working.

If anyone is still experiencing this after ensuring your user and pass is correct, generate a token at account settings>security>new access token , I was struggling for an hour but using a token worked. Don't know why

On Windows:
Right click docker on the system tray and sign out. Then sign in but use your docker hub username not email address.

For logging into hub.docker.com, what worked for me was make sure you DO NOT specify 'hub.docker.com'!!! Different versions of API-DNS? All of this after I spent a good hour changing my password, changing my token, etc.
Just simply:
docker login --username=myusername <enter>
theToken <enter>

Adding special characters like # in password may mess-up login to docker from terminal , even if we use correct case and everything else correct . But it will work from website if we use a special char in password.
So basically use letters and number only in password , don't use special char for docker login

docker login
Do not use email id. Use your username in smallcase and then give password.
You should be successfully login.

please login with your DOCKER ID and password
this would work instantly

Related

Pushing docker image to gitlab fails: unauthorized

I'm trying to push an image to my gitlab registry which i previously built with success.
docker login registry.gitlab.com
I give the credentials and it returns me a "Login Succeeded"
Then, as always, i do a
docker push registry.gitlab.com/username/registry/base:latest
And it ends with
unauthorized: authentication required
i already tried to
docker logout registry.gitlab.com
and login again.
The process can be found here, it's pretty simple
link to github/gitlabhq
I'm used to do it like that, first time i face the issue, don't understand
Any help appreciated !
Ensure that your account has read/write access to the registry you are trying to access. What you might need to do is to create a new Access Token as there is a difference between API/Access tokens and your "normal" user password. Use this access token as described in the documentation (https://github.com/gitlabhq/gitlabhq/blob/master/doc/user/packages/container_registry/index.md#authenticate-with-the-container-registry)
docker login registry.example.com -u <username> -p <token>
The token can be created by going to Edit Profile -> Access Tokens -> Select Scopes -> Ticking off 'Read registry' & 'Write registry'
The Gitlab support told me this is due to a native limitation of the token duration.
You cannot customize this duration in Saas mode.
So pushing large image results in auto logout.

Gitlab test out with Docker: ' You have signed up successfully. However, we could not sign you in because your account is awaiting approval...'

I have set up gitlab locally on ubuntu laptop per some help from this post. My set up is 100% exact to per that post. When I ran docker-compose up and visited localhost:54321 I was shown a screen to 'update my password'. I entered a new password then got taken to the sign in page where I clicked to sign up with a new account. I entered my name, email and password and hit register. I then saw this message:
I'm confused since I'm hosting gitlab locally via docker.Who is my gitlab administrator?!
How can I register on a locally hosted gitlab instance via docker? My ultimate goal is just a hello world - I'd like to explore the gitlab interface and see what the tool is all about.
The initial admin user for the GitLab CE is root.
In the GitLab Docker container path /etc/gitlab, there will be a file called "initial_root_password". Cat the content and you can got the initial password of the user root
Steps:
Assume the docker container name is gitlab_web_1
Go to the Docker container: docker exec -ti gitlab_web_1 /bin/bash
List item: cat /etc/gitlab/initial_root_password
Once you login with the user root successfully, you can try to manage the user account, and you can also use your own account to login.
Based on This Page
https://forum.gitlab.com/t/after-gitlab-ce-installation-on-ubuntu/32896
Username and Password default Administrator after Install Gitlab-ce:
Username: root
Password: 5iveL!fe
When opening the web interface after first running the container, you are prompted to 'change password'. Enter a password then on the next page enter username 'root' and the password you just created. I had to rerun the container and first empty everything in the set up directories. Emptied everything in data/, logs/ and config/ and then docker-compose up. That allowed me to login

Docker login: access denied you must use a personal access token

Trying to login from docker to gitlab using the command:
sudo docker login registry.gitlab.com?private_token=XXX
But I still have the following error message:
Error response from daemon: Get https://registry.gitlab.com/v2/: unauthorized: HTTP Basic: Access denied\nYou must use a personal access token with 'api' scope for Git over HTTP.\nYou can generate one at https://gitlab.com/-/profile/personal_access_tokens
The token has the right access I doubled checked... I am rather new to docker, any hint/help? thanks!
The correct command line (that works in my case at least) was:
docker login registry.example.com -u <your_username> -p <your_personal_access_token>
If you are using 2 factor authentication, then personal access tokens are required.
More information on the following webpage,
https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html
According to https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html, your username actually gets ignored:
Though required, GitLab usernames are ignored when authenticating with a personal access token. There is an issue for tracking to make GitLab use the username.
So, if you're not able to connect, it might not be because of the username.

What is the default admin password for DRONE_ADMIN users?

On first installation using a docker-compose file and following the installation instructions what is the default password for Closed Registration DRONE_ADMIN users?
The web frontend won't let you access it without a logon and it's not possible to create new users using the CLI without a login either.
The administrative user needs to login with the Gogs username and password
Drone will prompt you for a username and password to authenticate. You
should use your Gogs username and password. This is unfortunately
required due to Gogs lack of oauth2 support.
Let's use this example configuration for reference:
DRONE_ADMIN=johnsmith
You need to make sure that johnsmith is a valid Gogs username. When you are prompted to login you should enter johnsmith for the username, and use johnsmith's Gogs password.

Docker hello-world: authentication error

I'm just getting started with docker. I'm following the instructions specified here https://docs.docker.com/windows/step_one/
I installed docker (1.10.2) on windows 10 & ran docker run hello-world . But, I'm getting an authentication error while the tutorial doesn't mentioned anything about it.
Here's the message I received.
$ docker run hello-world
Unable to find image 'hello-world:latest' locally
docker: Error response from daemon: Authentication is required: Get https://registry-1.docker.io/v2/library/hello-world/manifests/latest: unauthorized: incorrect username or password.
See 'C:\Program Files\Docker Toolbox\docker.exe run --help'.
I searched google & here, but couldn't find anything similar to this error message.
Thanks!
Please run docker login at first time when you run any other docker commands.
You can log into any public or private repository for which you have credentials. When you log in, the command stores encoded credentials in $HOME/.docker/config.json on Linux or%USERPROFILE%/.docker/config.json on Windows.
If you login through your emailId it does not works.
On windows login using your docker hub id.
You can access by your username.
Probably it can happen if you were logged in before, by console or by kitematic.
You can try docker logout if you want use docker without auth.
In this case Authentication is required: shouldn't appear again.
I have solved this issue in macOS Mojave (version : 10.14.3)
docker login
Login with your username not email id then its working fine.
On macOS you need to login from the commandline using
docker login
Also you must use your username and not your email
on ubuntu:
docker login
so if you don't know your username password, you probably haven't created one.
what you should do, is go and create an id on docker
visit: official docker webpage
just like any other github accout ,they will ask you for the username, provide one and they will authenticate same as github, once done , put your email and password. verify it and you are now good to go.
ok! now coming to the point...
if you were facing the problem like the problem statement ,
just do
docker login
enter username and password, that you just provided .
you will be displayed ,"LOGIN succeeded"
now run this command
docker run hello-world
beware of the dash '-' sign , i myself stuck with this issue, and you are done.
thanks:)
run docker login to execute any other docker commands. or just logout if you want to use public hubs docker logout
For worked trying docker logout and then docker login with the proper credentials
For those who logged in via their email address associated with their account during the Docker desktop installation process - this problem seems to occur because the terminal has also stored those credentials, but for some reason it only accepts login's via your actual username.
If you go to DockerHub you should see it in the upper right corner.
Try running docker login with that username, and you should be all set!
docker login
# username from dockerhub
# the same password
Setting my vNAT for docker dns server to 8.8.8.8 resolved my issue on windows just try might help thanks

Resources