Irresponsive sign in button after docker desktop installation
Description
When i installed docker desktop on my linux machine it first prompted me with the login thing continue with google , github n all but it was doing nothing
Reproduce
But after a while like almost running the client 3- 4 times then it showed a error message which redirected me to this link https://docs.docker.com/desktop/setup/sign-in/ where i had to generate the gpg key using
gpg --generate-key
followed by:
pass init your-gpg-key
then it signed me in but this thing should be done at the post installation itself why after running you client after many times then u get to sign in
Expected behavior
Although i can now sign in but the problem still lies with sign in button not responding during first installation and the first login page itself when we freshly start docker desktop
docker version
Client: Docker Engine - Community
Version: 27.3.1
API version: 1.47
Go version: go1.22.7
Git commit: ce12230
Built: Fri Sep 20 11:41:19 2024
OS/Arch: linux/amd64
Context: desktop-linux
Server: Docker Desktop 4.35.1 (173168)
Engine:
Version: 27.3.1
API version: 1.47 (minimum version 1.24)
Go version: go1.22.7
Git commit: 41ca978
Built: Fri Sep 20 11:41:11 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.21
GitCommit: 472731909fa34bd7bc9c087e4c27943f9835f111
runc:
Version: 1.1.13
GitCommit: v1.1.13-0-g58aa920
docker-init:
Version: 0.19.0
GitCommit: de40ad0
docker info
docker info
Client: Docker Engine - Community
Version: 27.3.1
Context: desktop-linux
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.17.1-desktop.1
Path: /usr/lib/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.29.7-desktop.1
Path: /usr/lib/docker/cli-plugins/docker-compose
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.37
Path: /usr/lib/docker/cli-plugins/docker-debug
desktop: Docker Desktop commands (Alpha) (Docker Inc.)
Version: v0.0.15
Path: /usr/lib/docker/cli-plugins/docker-desktop
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: /usr/lib/docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.27
Path: /usr/lib/docker/cli-plugins/docker-extension
feedback: Provide feedback, right in your terminal! (Docker Inc.)
Version: v1.0.5
Path: /usr/lib/docker/cli-plugins/docker-feedback
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.3.0
Path: /usr/lib/docker/cli-plugins/docker-init
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: /usr/lib/docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.14.0
Path: /usr/lib/docker/cli-plugins/docker-scout
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 27.3.1
Storage Driver: overlayfs
driver-type: io.containerd.snapshotter.v1
Logging Driver: json-file
Cgroup Driver: cgroupfs
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: 472731909fa34bd7bc9c087e4c27943f9835f111
runc version: v1.1.13-0-g58aa920
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
cgroupns
Kernel Version: 6.10.11-linuxkit
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 959.4MiB
Name: docker-desktop
ID: bebf9c0e-d540-41ea-83c5-5f5268f05e0e
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Labels:
com.docker.desktop.address=unix:///home/harsh/.docker/desktop/docker-cli.sock
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
127.0.0.0/8
Live Restore Enabled: false
WARNING: daemon is not using the default seccomp profile
Diagnostics ID
94FF60EA-DC7B-4ECE-AAA5-F084B0CF3574/20241115175225
Additional Info
No response
even i faced the same issue :(
Same issue for me, new Latest Arch instillation, current docker desktop version 4.35.1
Thank you for bringing this issue to our attention. We're actively tracking it and working on a fix to clarify the required pass initialization step. In the meantime, we recommend following the guide: https://docs.docker.com/go/linux-credentials/
I did the initialization steps accurately and correctly using my generated key 72288B316646E9E52F661FE1E37742B5847A869E that I'm told expires 2027-11-24 under the name and email Jada @.***
On Mon, Nov 25, 2024, 2:09 PM marisimon @.***> wrote:
Thank you for bringing this issue to our attention. We're actively tracking it and working on a fix to clarify the required pass initialization step. In the meantime, we recommend following the guide: https://docs.docker.com/go/linux-credentials/
— Reply to this email directly, view it on GitHub https://github.com/docker/desktop-linux/issues/261#issuecomment-2498825810, or unsubscribe https://github.com/notifications/unsubscribe-auth/BIWARX5LOPXUC47M7C5UXMD2CNYYFAVCNFSM6AAAAABR3VYGRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJYHAZDKOBRGA . You are receiving this because you commented.Message ID: @.***>
Same here , since I had a lot of issues with the desktop I have now switched to docker cli, docker desktop kind of sucks
Thats a bummer, I hope I don't have the same sign in trouble with docker CLI
On Mon, Dec 2, 2024, 12:30 AM Harsh Govardhanlal Gupta < @.***> wrote:
Same here , since I had a lot of issues with the desktop I have now switched to docker cli, docker desktop kind of sucks
— Reply to this email directly, view it on GitHub https://github.com/docker/desktop-linux/issues/261#issuecomment-2510614751, or unsubscribe https://github.com/notifications/unsubscribe-auth/BIWARXZR77IWJ6S3A2SFJCT2DPWARAVCNFSM6AAAAABR3VYGRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJQGYYTINZVGE . You are receiving this because you commented.Message ID: @.***>
No u won't, unless u want to pull a private docker image then only this authentication process is needed i think so rest u are good to go moreover the cli does everything that the desktop does and it comparatively uses less resources like ram and storage
Sorry that I'm new to this, but do I uninstall docker desktop and the binary before installing docker CLI?
On Mon, Dec 2, 2024, 12:38 AM Harsh Govardhanlal Gupta < @.***> wrote:
No u won't, unless u want to pull a private docker image then only this authentication process is needed i think so rest u are good to go moreover the cli does everything that the desktop does and it comparatively uses less resources like ram and storage
— Reply to this email directly, view it on GitHub https://github.com/docker/desktop-linux/issues/261#issuecomment-2510622940, or unsubscribe https://github.com/notifications/unsubscribe-auth/BIWARX2QO4FRATGVDGU4LVD2DPW5LAVCNFSM6AAAAABR3VYGRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJQGYZDEOJUGA . You are receiving this because you commented.Message ID: @.***>
It's not mandatory to uninstall docker desktop to do it so but if u are comfortable using desktop then don't uninstall tbh its UI good enough for beginners and it does all the work cli does its ur wish at the end better stick to desktop then if u want to switch to cli go ahead make sure u read the docker docs
Okay, thank you!
On Mon, Dec 2, 2024, 12:52 AM Harsh Govardhanlal Gupta < @.***> wrote:
It's not mandatory to uninstall docker desktop to do it so but if u are comfortable using desktop then don't uninstall tbh its UI good enough for beginners and it does all the work cli does its ur wish at the end better stick to desktop then if u want to switch to cli go ahead make sure u read the docker docs
— Reply to this email directly, view it on GitHub https://github.com/docker/desktop-linux/issues/261#issuecomment-2510639365, or unsubscribe https://github.com/notifications/unsubscribe-auth/BIWARX2RD6JXKO4B5VL34N32DPYTNAVCNFSM6AAAAABR3VYGRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJQGYZTSMZWGU . You are receiving this because you commented.Message ID: @.***>