Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Every docker command I issue has a 15 sec lag time #4649

Closed
2 tasks done
terrywbrady opened this issue Sep 4, 2019 · 7 comments
Closed
2 tasks done

Every docker command I issue has a 15 sec lag time #4649

terrywbrady opened this issue Sep 4, 2019 · 7 comments

Comments

@terrywbrady
Copy link

  • I have tried with the latest version of my channel (Stable or Edge)
  • I have uploaded Diagnostics
  • Diagnostics ID: 15196998-31A4-4AAE-BC05-A68A30886AEC/20190904163245

Expected behavior

Timely response to docker cli commands.

Actual behavior

Every docker command I issue has a 15 - 20 sec lag time.

Information

  • Windows Version: Windows 10 Enterprise ver 1809
  • Docker Desktop Version: 2.1.0.2 (37877)
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM:

Steps to reproduce the behavior

  1. ...
  2. ...
@terrywbrady
Copy link
Author

This seems similar to #1936. Please advise if there is a workaround I should try.

@terrywbrady
Copy link
Author

This issue resolved itself after I resolved an issue with my firewall.

@terrywbrady
Copy link
Author

This problem has returned.

$ time docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

real    1m14.760s
user    0m0.000s
sys     0m0.015s

$ time docker version
Client: Docker Engine - Community
 Version:           19.03.2
 API version:       1.40
 Go version:        go1.12.8
 Git commit:        6a30dfc
 Built:             Thu Aug 29 05:26:49 2019
 OS/Arch:           windows/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.2
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.8
  Git commit:       6a30dfc
  Built:            Thu Aug 29 05:32:21 2019
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.2.6
  GitCommit:        894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc:
  Version:          1.0.0-rc8
  GitCommit:        425e105d5a03fabd737a126ad93d62a9eeede87f
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

real    1m14.849s
user    0m0.015s
sys     0m0.015s

@terrywbrady terrywbrady reopened this Sep 5, 2019
@terrywbrady
Copy link
Author

This problem is significantly worsened with VPN is enabled. I have not yet determined if disabling VPN is entirely the cause of the issue.

@marcello-mirenda
Copy link

marcello-mirenda commented Oct 13, 2019

Same problem. Docker Desktop version 2.1.0.3. Windows added to a domain. Every command has a 23 secs lag time. Wait a bit after a test and the other.
Note: if the machine is attached at the domain network the response time reduces to 430 milliseconds.

$start = [System.Diagnostics.Stopwatch]::StartNew()
& docker images
$start.Stop()
Write-Output $start.Elapsed
D:\wd\repo\docker-2103-too-slow

REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE

Days              : 0
Hours             : 0
Minutes           : 0
Seconds           : 23
Milliseconds      : 358
Ticks             : 233580843
TotalDays         : 0.000270348197916667
TotalHours        : 0.00648835675
TotalMinutes      : 0.389301405
TotalSeconds      : 23.3580843
TotalMilliseconds : 23358.0843
=> docker system info                                                                                                                                                   Client:
 Debug Mode: false

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 0
 Server Version: 19.03.2
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 894b81a4b802e4eb2a91d1ce216b8817763c29fb
 runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
 init version: fec3683
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 4.9.184-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: x86_64
 CPUs: 2
 Total Memory: 1.952GiB
 Name: docker-desktop
 ID: OAFK:KCMU:M4YE:7CG4:UL6D:TZVY:VGTR:H75I:Y7DD:DAM4:J4SG:DAHZ
 Docker Root Dir: /var/lib/docker
 Debug Mode: true
  File Descriptors: 28
  Goroutines: 42
  System Time: 2019-10-13T16:10:25.3001295Z
  EventsListeners: 1
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
 Product License: Community Engine

@docker-robott
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jul 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants