search

docker / for-win

Bug reports for Docker Desktop for Windows
https://www.docker.com/products/docker#/windows
1.86k stars 291 forks source link

Overlapping Networks #13211

Open YouveGotMeowxy opened 1 year ago

YouveGotMeowxy commented 1 year ago

Actual behavior

I'm getting this error. The IP's and docker containers change upon restart of DD, but I always get at least 1 of these. Notice they are from the "Extension" containers all the time, and AFAIK there's no way to alter the Compose file/subnet for them:

[WARN] DD0032: do Docker networks overlap with host IPs? network aquasec_trivy-docker-extension-desktop-extension_default has subnet 172.20.0.0/16 which overlaps with host IP 172.20.240.1

Please note the following 1 warning:

1 : The check: do Docker networks overlap with host IPs?
    Produced the following warning: network aquasec_trivy-docker-extension-desktop-extension_default has subnet 172.20.0.0/16 which overlaps with host IP 172.20.240.1

If the subnet used by a Docker network overlaps with an IP used by the host, then containers
won't be able to contact the overlapping IP addresses.

Try configuring the IP address range used by networks: in your docker-compose.yml.
See https://docs.docker.com/compose/compose-file/compose-file-v2/#ipv4_address-ipv6_address

Expected behavior

No error. ;)

Information

Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check

Click ``` [2023-02-01T22:31:24.759757800Z][com.docker.diagnose.exe][I] set path configuration to OnHost Starting diagnostics [PASS] DD0027: is there available disk space on the host? [PASS] DD0028: is there available VM disk space? [PASS] DD0002: does the bootloader have virtualization enabled? [SKIP] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled? [PASS] DD0021: is the WSL 2 Windows Feature enabled? [PASS] DD0024: is WSL installed? [PASS] DD0025: are WSL distros installed? [PASS] DD0026: is the WSL LxssManager service running? [PASS] DD0029: is the WSL 2 Linux filesystem corrupt? [PASS] DD0035: is the VM time synchronized? [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] DD0003: is the Docker CLI working? [PASS] DD0005: is the user in the docker-users group? [PASS] DD0038: is the connection to Docker working? [PASS] DD0014: are the backend processes running? [PASS] DD0007: is the backend responding? [PASS] DD0008: is the native API responding? [PASS] DD0009: is the vpnkit API responding? [PASS] DD0010: is the Docker API proxy responding? [PASS] DD0006: is the Docker Desktop Service responding? [SKIP] DD0030: is the image access management authorized? [PASS] DD0033: does the host have Internet access? [PASS] DD0002: does the bootloader have virtualization enabled? [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled? [PASS] DD0021: is the WSL 2 Windows Feature enabled? [PASS] DD0024: is WSL installed? [PASS] DD0025: are WSL distros installed? [PASS] DD0026: is the WSL LxssManager service running? [PASS] DD0029: is the WSL 2 Linux filesystem corrupt? [PASS] DD0035: is the VM time synchronized? [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? [WARN] DD0032: do Docker networks overlap with host IPs? network aquasec_trivy-docker-extension-desktop-extension_default has subnet 172.20.0.0/16 which overlaps with host IP 172.20.240.1 Please note the following 1 warning: 1 : The check: do Docker networks overlap with host IPs? Produced the following warning: network aquasec_trivy-docker-extension-desktop-extension_default has subnet 172.20.0.0/16 which overlaps with host IP 172.20.240.1 If the subnet used by a Docker network overlaps with an IP used by the host, then containers won't be able to contact the overlapping IP addresses. Try configuring the IP address range used by networks: in your docker-compose.yml. See https://docs.docker.com/compose/compose-file/compose-file-v2/#ipv4_address-ipv6_address No fatal errors detected. ```

May or may not be related somehow to this, since they happened with the same update: https://github.com/docker/for-win/issues/13187

jirisykora83 commented 1 year ago

Did you find any workaround? I cannot even uninstall that extensions.... it is joke

edit: I end up with complete reinstalling the whole docker for windows is complete trash as every few releases I end up with solving something what broke itself...

YouveGotMeowxy commented 1 year ago

Did you find any workaround? I cannot even uninstall that extensions.... it is joke

Unfortunately not, and the Docker devs don't even pay attention to their own GH issues/users reporting issues.

I haven't even been able to use any containers at all for about a week or so because of this last update, and zero dev support.

gtardif commented 1 year ago

Thank you for the feedback. It seems the Trivy Docker extension has some collision with your network settings. If you want to see some details about the container started by the extension, you can turn on a setting to make these containers and compose stack visible.

Since this is an issue with the extension itself, you can report the issue on Trivy's extension issue tracker.

docker-robot[bot] commented 1 year ago

There hasn't been any activity on this issue for a long time. If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment. If not, this issue will be closed in 30 days.

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

/lifecycle stale