Share and learn in the Docker community.
Hi all!
I have some problems with Docker Desktop. When I start Docker Desktop, it creates vEthernet(WSL) network adapter (Hyper-V). And after that, my local corporate network became very slow. MS Outlook works very slow also. If i stop Docker and restart my PC, everything works perfect.
How can I solve this issue? Can anyone have this problem?
What happens when you start a WSL distribution without running Docker?
This is just a guess, but if running WSL or Docker makes your network slow and not just the container network, then your corporate network might have a colliding IP address with your WSL network. Maybe your DNS server or a gateway. You can try to run TRACERT on Windows to trace your network routes to an IP address. If you packages have to be resent multiple times before they can actually be sent out, that can slow your traffic.
Run it multiple times until you see a difference in the routing. If you also see that it doesn’t work in one direction, that can help to resolve the issue.
On second thought, if you have IP issues, tracert will not help, but it is still useful.
Hi @rimelek,
Thanks for reply. I’m not running WSL separatly, I’m not sure I can launch this. I just start DockerDesktop.
Funny things is, when I stop DockerDesktop, I still have vEthernet atapter available. Looks like Docker create this adapter with start, and doesnt remove it. When I restart my PC, this vEthernet adapter also removes automatically. And creates with Docker start.
Even if I disable manually, local network still slow. I need restart PC to make speed fast.
Looks like some issues with this vEthernet adapter.
PS TRACERT shows everything is OK.
Docker doesn’t create the network adapter. WSL does. And that adapter will be there until you restart your machine. This is why I suggested to try tun run a WSL distribution to find out if the problem is Docker or WSL behind Docker which is more likely I think.
Ok, I’ll try. Thanks
Hi @rimelek, I’ve tried WSL with Ubuntu/Redis, and it looks like it works fine. There is no any vEthernet adapter appears. And my network and Outlook works fine.
Problem starts when I launch DockerDesktop.
Can you pls suggest anything else?
Please, share the output of
docker info
Use code blocks as I did above. (</> button)
When I start Docker Desktop, my network interface like this:
Ethernet adapter vEthernet (WSL)
You mentioned something similar, but I don’t have any Hyper-V in the name of the adapter. And you should not have either.
Hi!
Here is ‘docker info’
PS C:\Windows\system32> docker info
Client:
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc., v0.8.2)
compose: Docker Compose (Docker Inc., v2.7.0)
extension: Manages Docker extensions (Docker Inc., v0.2.8)
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0)
scan: Docker Scan (Docker Inc., v0.17.0)
Server:
Containers: 3
Running: 2
Paused: 0
Stopped: 1
Images: 2
Server Version: 20.10.17
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
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: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1
runc version: v1.1.2-0-ga916309
init version: de40ad0
Security Options:
seccomp
Profile: default
Kernel Version: 5.10.16.3-microsoft-standard-WSL2
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 12
Total Memory: 5.947GiB
Name: docker-desktop
ID: SXUR:3A6M:JYZK:RTQP:ZVAD:ZZPG:N356:7ITT:AZE3:MBIE:64E6:5CXA
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
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5000
127.0.0.0/8
Live Restore Enabled: false
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
PS C:\Windows\system32>
Weird. Looks like your installation is right, but I still don’t understand the adapter. Maybe I missed it on my system, but I don’t remember that “Hyper-V” in the description of the adapter and I searched for it. I will check it again when I am home, but I don’t know what could have happened. Docker Desktop should not affect your LAN network at all.
