This repository was archived by the owner on Mar 24, 2020. It is now read-only.

Description
I'm not sure if the latest merged PR #45 was intended to be consumed publicly, but the kernel image resulting from building at that SHA will not launch containers in my environment.
I left some comments already at #45 (comment) with more specifics of my environment / build process / etc.
I bring this up because of the problems I'm seeing with DNS resolution in LCOW + Alpine that I raised in - microsoft/opengcs#303
Maybe this is an issue that's been addressed already in the dependency bumps, but I can't use it at the moment.
To recap the linked comments, this is what my Docker environment looks like:
Client:
Debug Mode: false
Plugins:
app: Docker Application (Docker Inc., v0.8.0-beta2)
buildx: Build with BuildKit (Docker Inc., v0.2.0-6-g509c4b6-tp)
Server:
Containers: 3
Running: 0
Paused: 0
Stopped: 3
Images: 59
Server Version: master-dockerproject-2019-04-28
Storage Driver: windowsfilter (windows) lcow (linux)
Windows:
LCOW:
Logging Driver: json-file
Plugins:
Volume: local
Network: ics l2bridge l2tunnel nat null overlay transparent
Log: awslogs etwlogs fluentd gcplogs gelf json-file local logentries splunk syslog
Swarm: inactive
Default Isolation: hyperv
Kernel Version: 10.0 17763 (17763.1.amd64fre.rs5_release.180914-1434)
Operating System: Windows 10 Enterprise Version 1809 (OS Build 17763.437)
OSType: windows
Architecture: x86_64
CPUs: 2
Total Memory: 16GiB
Name: ci-lcow-prod-1
ID: 0ac02c9d-aaba-42f4-8749-5a64af3068d8
Docker Root Dir: C:\ProgramData\docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: true
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Thanks!