I'm having an issue with a specific database engine (proprietary) inside a docker container on windows (LCOW).
I've managed to narrow it down to the use of vpnkit.
Here is the situation:
I start the container with few ports forwarded -p 6000:6000 -p 6001:6001 -p 1025-1035:1025-1035
I spawn an ODBC client on my Windows host, connect it to localhost, and query this db (multiple insert, approx. 4000 ).
At some point the connection is closed, with a generic ODBC exception. Neither the db engine, nor the odbc client logs explains the situation, it seems related to a network issue.
Tail of the last TCP exchanges using localhost/vpnkit
When I do the same thing but connect the ODBC client to the hyper-v VM (MobyLinux) ip (in my case 10.0.75.2), everything works fine.
I'm guessing vpnkit has an impact on the network between the db engine and the odbc client, but it's not clear what exactly. I've read vpnkit has some sort of protocol over-the-top to handle connection close. Is there an impact on packet size ? MTU ? or anything else.
I also suppose the db engine or the odbc client is not quite resilient to network perturbation.
docker version
Client:
Version: 18.06.1-ce
API version: 1.38
Go version: go1.10.3
Git commit: e68fc7a
Built: Tue Aug 21 17:21:34 2018
OS/Arch: windows/amd64
Experimental: false
Server:
Engine:
Version: 18.06.1-ce
API version: 1.38 (minimum version 1.12)
Go version: go1.10.3
Git commit: e68fc7a
Built: Tue Aug 21 17:29:02 2018
OS/Arch: linux/amd64
Experimental: false
I'm having an issue with a specific database engine (proprietary) inside a docker container on windows (LCOW). I've managed to narrow it down to the use of vpnkit.
Here is the situation: I start the container with few ports forwarded
-p 6000:6000 -p 6001:6001 -p 1025-1035:1025-1035
I spawn an ODBC client on my Windows host, connect it to localhost, and query this db (multiple insert, approx. 4000 ). At some point the connection is closed, with a generic ODBC exception. Neither the db engine, nor the odbc client logs explains the situation, it seems related to a network issue.Tail of the last TCP exchanges using localhost/vpnkit
When I do the same thing but connect the ODBC client to the hyper-v VM (MobyLinux) ip (in my case 10.0.75.2), everything works fine.
I'm guessing vpnkit has an impact on the network between the db engine and the odbc client, but it's not clear what exactly. I've read vpnkit has some sort of protocol over-the-top to handle connection close. Is there an impact on packet size ? MTU ? or anything else. I also suppose the db engine or the odbc client is not quite resilient to network perturbation.
docker version
docker info
Thank you