Kubelet on Windows has many errors and exceptions

[anhowe]

The Windows Kubelet logs show many errors and exceptions from Kubelet because the Windows environment is different.

SO article shows these common errors:
http://stackoverflow.com/questions/43148284/azure-k8s-windows-cluster-internal-error-missing-stats-for-root-container

E0331 16:53:48.527868 900 eviction_manager.go:205] eviction manager: unexpected err: Missing stats for root container
E0331 16:53:55.757082 900 kubelet.go:1634] Failed to check if disk space is available for the runtime: could not determine capacity for "runtime" fs. Info: {Usage:0 Capacity:0 Available:0 Timestamp:2017-03-31 16:53:55.7570827 +0000 GMT}
E0331 16:53:55.757082 900 kubelet.go:1642] Failed to check if disk space is available on the root partition: could not determine capacity for "root" fs. Info: {Usage:0 Capacity:0 Available:0 Timestamp:2017-03-31 16:53:55.7570827 +0000 G
E0331 16:54:04.462246 900 handler.go:246] HTTP InternalServerError serving /stats/summary: Internal Error: Missing stats for root container

This issue is resolved once all common errors have disappeared from the first 5 minutes of startup.

[fohnwind]

Hi，I have this issue on Windows Server 2016 with docker 17.06.1-ee-1 and Kubelet v1.7.3.
Is there any solution so far?
Thanks

[jdumars]

This will be discussed in an upcoming SIG-Azure meeting.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[cmeiklejohn]

Was there any resolution to this issue? I'm also experiencing the following error, which is preventing container deployment.

Failed to check if disk space is available for the runtime: could not determine capacity