Open bantl23 opened 6 years ago
I have the same issue. The laptop could not be fresher, just got it yesterday from my new company. Its a Windows 7 Enterprise ... I installed virtualbox seperatly/before the docker-toolbox. I use Mingw64 too (but the issue exists in the docker-quickstart-terminal too). And as well: docker responds instantly when from inside, using (docker-machine ssh default before).
$ time docker version
Client:
Version: 18.03.0-ce
API version: 1.37
Go version: go1.9.4
Git commit: 0520e24302
Built: Fri Mar 23 08:31:36 2018
OS/Arch: windows/amd64
Experimental: false
Orchestrator: swarm
Server:
Engine:
Version: 18.03.1-ce
API version: 1.37 (minimum version 1.12)
Go version: go1.9.5
Git commit: 9ee9f40
Built: Thu Apr 26 07:23:03 2018
OS/Arch: linux/amd64
Experimental: false
real 0m22,208s
user 0m0,000s
sys 0m0,031s
info
$ time docker info
Containers: 2
Running: 1
Paused: 0
Stopped: 1
Images: 1
Server Version: 18.03.1-ce
Storage Driver: aufs
Root Dir: /mnt/sda1/var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 7
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 773c489c9c1b21a6d78b5c538cd395416ec50f88
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: 949e6fa
Security Options:
seccomp
Profile: default
Kernel Version: 4.9.93-boot2docker
Operating System: Boot2Docker 18.03.1-ce (TCL 8.2.1); HEAD : cb77972 - Thu Apr 26 16:40 :3 UTC 2018
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 995.6MiB
Name: default
ID: JMN7:QT5Q:IL2V:CYYC:WX6V:YLW7:KBM5:VGLM:UJ7D:4RXA:5FJP:PYY3
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
provider=virtualbox
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
real 0m21,237s
user 0m0,000s
sys 0m0,031s
@bantl23 I assume you're using Wi-Fi + bridged network to provide connectivity for your VirtualBox guest? Try Ethernet. Although not related to Docker, I'm experiencing the same slow connection with the Intel(R) Dual Band Wireless-AC 8265 Wi-Fi chip.
Previous laptop had 3165 and it was fine.
@bantl23 I assume you're using Wi-Fi + bridged network to provide connectivity for your VirtualBox guest? Try Ethernet. Although not related to Docker, I'm experiencing the same slow connection with the Intel(R) Dual Band Wireless-AC 8265 Wi-Fi chip.
Previous laptop had 3165 and it was fine.
when i disconnect the wifi,yeah, it becomes faster!
Try to disable all bridge protocols in the the advanced settings of your wifi adapter. Reference: https://superuser.com/a/540885 Afterwards "docker version" responds immediately.
Fresh install, when I execute
docker info
it takes about 3min30sec to return.When I use docker within the boot2docker vm (
docker-machine ssh default
) the response are very quick. So I think its somehow related to networking. However, I'm not sure what to look for to fix this. Any ideas?I've included output from
docker version
,docker info
,ipconfig /all
, androute print
Platform: Windows 10 VM Provider: Virtual Box Docker: Docker Toolbox
I'm using MINGW64 which has the time command
docker version:
docker info:
Virtualbox Network:
Routing: