moby: Login command says "The handle is invalid" after inputting username
To reproduce:
docker login [repo]
Username: [type username, hit Enter]
The handle is invalid.
But this command DOES work:
docker login --username [username] --password [password] --email [email] [repo]
WARNING: login credentials saved in [blah]
Login Succeeded
So the problem might be something to do with reading from stdin?
Vague, uninformed theory: could this ReadPassword issue be related?
docker version:
Client version: 1.7.1
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 786b29d
OS/Arch (client): windows/amd64
Server version: 1.7.0
Server API version: 1.19
Go version (server): go1.4.2
Git commit (server): 0baf609
OS/Arch (server): linux/amd64
docker info:
Containers: 3
Images: 76
Storage Driver: aufs
Root Dir: /mnt/sda1/var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 82
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.0.5-boot2docker
Operating System: Boot2Docker 1.7.0 (TCL 6.3); master : 7960f90 - Thu Jun 18 18:31:45 UTC 2015
CPUs: 8
Total Memory: 1.955 GiB
Name: boot2docker
ID: 3NB7:ICRC:QASK:SOLS:X5SQ:FWNP:LSL7:LGPP:FNE3:SO5H:MKPB:INIS
Debug mode (server): true
File Descriptors: 26
Goroutines: 47
System Time: 2015-08-03T21:45:53.563558526Z
EventsListeners: 0
Init SHA1:
Init Path: /usr/local/bin/docker
Docker Root Dir: /mnt/sda1/var/lib/docker
uname -a:
MINGW64_NT-6.3 mdnbepps 2.1.0(0.288/5/3) 2015-06-28 18:57 x86_64 Msys
About this issue
- Original URL
- State: closed
- Created 9 years ago
- Comments: 35 (15 by maintainers)
It looks like this is specific to the password field…?? Username is accepted in prompt or long form. email is accepted in prompt or long form. Password seems to be where it chokes.
But it worked for me using winpty.
Having the same issue here.
As workaround I did
docker-machine ssh <your_machine>
docker login <your_private_repo>
And then copied the persisted credentials in
~/.docker/config.json
to my host machine (windows).docker pull <your_private_repo>/<some_image>
Works as expected afterwards.