[X ] I have tried with the latest version of Docker Desktop
[ X] I have tried disabling enabled experimental features
Expected behavior
Successfully Sign in
Actual behavior
After sign in via web browser, Docker desktop hang with verifying credentials
Information
It is totally reproducible
OS Version: Unbuntu 20.04
Docker Desktop Version: 4.25.0
Steps to reproduce the behavior
run check
Starting diagnostics
[2023-11-12T15:00:00.014098905Z][com.docker.diagnose.ipc][I] ipc.NewClient: 5d8964b2-diagnose -> <HOME>/.docker/desktop/backend.sock BackendAPI
[2023-11-12T15:00:00.014285843Z][com.docker.diagnose.ipc][I] (b082e370) 5d8964b2-diagnose C->S BackendAPI POST /idle/make-busy
[2023-11-12T15:00:00.015140940Z][com.docker.diagnose.ipc][I] (b082e370) 5d8964b2-diagnose C<-S 1d2c5756-BackendAPI POST /idle/make-busy (836.477µs): 0xc000012be0
[2023-11-12T15:00:01.015167839Z][com.docker.diagnose.ipc][I] (b7caa898) 5d8964b2-diagnose C->S BackendAPI GET /idle
[2023-11-12T15:00:01.017082880Z][com.docker.diagnose.ipc][I] (b7caa898) 5d8964b2-diagnose C<-S 1d2c5756-BackendAPI GET /idle (1.789625ms): {"apisInFlight":{},"booted":true,"busyReason":["timed activities: map[/idle/make-busy:28.998815711s]"],"containers":0,"idle":"bool","kubernetesEnabled":false,"reduced":false,"services":0,"timedActivities":{"/idle/make-busy":"float64"},"vmPaused":false,"vmRunning":true,"vmStopped":false,"windowsContainers":false}
[PASS] DD0039: are KVM user permissions configured?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0034: is Context set to a Docker Desktop context?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0038: is the connection to Docker working?
[FAIL] DD0014: are the backend processes running? 1 error occurred:
* querying com.docker.backend process: is it running as a different user?: readlink /proc/304948/exe: permission denied
[FAIL] DD0007: is the backend responding? prereq failed: are the backend processes running?
[FAIL] DD0009: is the vpnkit API responding? prereq failed: are the backend processes running?
[FAIL] DD0010: is the Docker API proxy responding? prereq failed: are the backend processes running?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0037: is the virtiofs setup correct?
[PASS] DD0036: is the credentials store configured correctly?
[PASS] DD0033: does the host have Internet access?
[PASS] DD0039: are KVM user permissions configured?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0032: do Docker networks overlap with host IPs?
Please investigate the following 1 issue:
1 : The test: are the backend processes running?
Failed with: 1 error occurred:
* querying com.docker.backend process: is it running as a different user?: readlink /proc/304948/exe: permission denied
pengxurui
commented
6 months ago
Description
Description
Expected behavior
Successfully Sign in
Actual behavior
After sign in via web browser, Docker desktop hang with verifying credentials
Information It is totally reproducible
Steps to reproduce the behavior
run check
Not all of the backend processes are running.
Reproduce
start docker
Expected behavior
No response
docker version
docker info
Additional Info
No response
Reproduce
start docker
Expected behavior
sign in
docker version
docker info
Diagnostics ID
8b47929c-3cdf-4fb1-bac0-b991057defba/20231112145911
Additional Info
No response