Problem creating working docker linux vm on windows 7.1

[bmckinle]

We have encountered a problem creating a working docker default vm on two similar Windows 7.1 boxes. We are running kitematic (docker tool) to create a (default) vm and run docker images. We have attached the vbox.log. There appears to be network driver errors coming from the C++ code in DrvIntNet.cpp:1752, as the excerpt below suggests. Can you suggest what might be causing the problem based on the log? If you need further information, let me know and I'll provide it. Thanks! Note: I have been able to run the same docker installer version on a third windows 7.1 box and have encountered no vm creation or usage issues.

0:00:01.688381 IntNet#0: szNetwork={HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2} enmTrunkType=3 szTrunk={\DEVICE\{98CC1577-EC55-4AE7-96D7-AF00039194BC}} fFlags=0x8000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:01.688462 VMSetError: F:\tinderbox\win-rel\src\VBox\Devices\Network\DrvIntNet.cpp(1752) int __cdecl drvR3IntNetConstruct(struct PDMDRVINS *,struct CFGMNODE *,unsigned int); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:01.688483 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2'
00:00:01.688531 VMSetError: F:\tinderbox\win-rel\src\VBox\Devices\Network\DevE1000.cpp(7714) int __cdecl e1kR3Construct(struct PDMDEVINS *,int,struct CFGMNODE *); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:01.688534 VMSetError: Failed to attach the network LUN
00:00:01.688551 PDM: Failed to construct 'e1000'/1! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found.

I have attached the network configuration associated with vbox.log. The failing vm creation attempts are also associated with "secured" win7 boxes in a large organization. With bridging subnets and such involved, it appears we may need to adjust the docker file to accommodate. Not sure. Another point is that on one failing box, we can install a late model FC kernel and it works just fine. It uses a single network adapter, unlike the bridging setup of docker. I suspect we need some advanced network setup help with docker's default vm. What is causing the vbox problem?

[prbp]

The NDIS6 driver used for Host-Only adapter has problems. You should try the NDIS5 driver. Chech this thread viewtopic.php?f=6&t=70199.