docker / for-linux

Docker Engine for Linux
https://docs.docker.com/engine/installation/
756 stars 85 forks source link

docker login fails with 500 Internal server error and EOF #1494

Open hemna opened 7 months ago

hemna commented 7 months ago

I'm using ubuntu 22.04 and trying to run docker login. It fails with EOF Error response. Running strace on docker login shows that the socket reads an error from the remote server of 500 Internal server error.

└─> docker login
Authenticating with existing credentials...
Login did not succeed, error: Error response from daemon: Get "https://registry-1.docker.io/v2/": EOF
Log in with your Docker ID or email address 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.
You can log in with your password or a Personal Access Token (PAT). Using a limited-scope PAT grants better security and is required for organizations using SSO. Learn more at https://docs.docker.com/go/access-tokens/

Username (hemna6969):
Password:
Error response from daemon: Get "https://registry-1.docker.io/v2/": EOF

Strace docker login

...
mmap(NULL, 262144, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0Authenticating with existing credentials...
) = 0x7f7f1c6ab000
futex(0x55e881e388e8, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0x55e881e388e8, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x55e881e388e8, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0x55e881e388e8, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
epoll_pwait(4, Login did not succeed, error: Error response from daemon: Get "https://registry-1.docker.io/v2/": EOF
Username (hemna6969): [], 128, 0, NULL, 0)     = 0
epoll_pwait(4,
Password:
[{events=EPOLLOUT, data={u32=1851260931, u64=9187094752059195395}}], 128, -1, NULL, 0) = 1
epoll_pwait(4, [], 128, 0, NULL, 0)     = 0
epoll_pwait(4, [{events=EPOLLIN|EPOLLOUT, data={u32=1851260931, u64=9187094752059195395}}], 128, -1, NULL, 0) = 1
futex(0x55e881e38ca0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x55e881e38bb8, FUTEX_WAKE_PRIVATE, 1) = 1
read(3, "HTTP/1.1 500 Internal Server Err"..., 4096) = 279
futex(0xc000098948, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xc000600148, FUTEX_WAKE_PRIVATE, 1) = 1
Error response from daemon: Get "https://registry-1.docker.io/v2/": EOF

docker info

└─> docker info
Client: Docker Engine - Community
 Version:    26.0.0
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.13.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.25.0
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 10
  Running: 9
  Paused: 0
  Stopped: 1
 Images: 11
 Server Version: 26.0.0
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 5.15.0-101-generic
 Operating System: Ubuntu 22.04.4 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 24
 Total Memory: 118GiB
 Name: dl360-1
 ID: 49f3976c-b8ab-4130-b2d4-351831967b98
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 105
  Goroutines: 137
  System Time: 2024-04-09T13:51:11.232119179-04:00
  EventsListeners: 3
 Username: hemna6969
 Experimental: true
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

[DEPRECATION NOTICE]: API is accessible on http://0.0.0.0:2376 without encryption.
         Access to the remote API is equivalent to root access on the host. Refer
         to the 'Docker daemon attack surface' section in the documentation for
         more information: https://docs.docker.com/go/attack-surface/
In future versions this will be a hard failure preventing the daemon from starting! Learn more at: https://docs.docker.com/go/api-security/
Samuel-MM commented 5 months ago

@hemna Did you find any solution?

huseyingoztok commented 6 days ago

Same problem @hemna did you find any solution?