Docker app to host mysql connection not working (host os & image = windows)

Question

My app from container wants to access Mysql from host machine, but is not able to connect. I googled a lot and tried many solutions but could not figure the error, could you please help me on this.

1. It is a windows image
2. IIS Website works
3. Website pages that use DB Connection does not work
4. Mysql DB is install in local machine (same pc where docker desktop is installed in)
5. Connection string in app uses 'host.docker.internal' with port 3306.

Tried docker uninstall, reinstall, image prune, container prune, WSL stop and start, host file commenting for below lines:

192.168.1.8 host.docker.internal
192.168.1.8 gateway.docker.internal

Below is the ipconfig from container

Nslookup and Ping commands:

network LS:

Docker Compose:

version: "3.9"
services:
    web:
        container_name: dinesh_server_container
        image: dinesh_server:1
        build: .
        ports:
            - "8000:80"
            - "8001:81"
        volumes:
            - .\rowowcf:c:\rowowcf
            - .\rowowcf_supportfiles:c:\rowowcf_supportfiles
            - .\rowocollectionsite:c:\rowocollectionsite
        environment:
            TZ: Asia/Calcutta

Build image uses: FROM mcr.microsoft.com/dotnet/framework/aspnet:4.8

Host OS: Win 10 Pro 10.0.19043 Build 19043

HyperV is enabled too.

Tried the below too:

extra_hosts:
    - "host.docker.internal:host-gateway"

Since it is on windows OS - host network mode is not supported (per my research)

EDIT: MYSQL Bind Address is 0.0.0.0:

Answer 1

Maybe the problem is not directly related to docker but to mysql.

Please, try making your local mysql database listen in all the network interfaces of your host: by default it only listens in 127.0.0.1 and for this reason perhaps docker is unable to connect to it.

I am not sure about how to do it in Windows but typically you need to provide the value 0.0.0.0 for the bind-address configuration option in mysqld.cnf:

bind-address = 0.0.0.0

Please, consider review as well this article or this related serverfault question.

From a totally different point of view, I found this and this other related open issues in the Docker for Windows repository that in a certain way resembles your problem: especially the first one provides some workaround for the problem, like shutting down the wsl backend and restarting the docker daemon. I doesn't look like a solution to me, but perhaps it could be of help.