OOMKilled flag never set on Windows.

[ecstatic-morse]

State.OOMKilled is never set when running docker inspect on a container on Windows, even if that container exceeded its memory limit. This is a known shortcoming; the test is explicitly skipped on Windows. I'm aware that the "OOM killer" is Linux specific, but perhaps there's a way to communicate that a container exceeded its memory limit on Windows as well.

[thaJeztah]

not sure if this is possible; I recall discussing this at some point with @johnstep, and don't think it is

/cc @jhowardmsft

[thaJeztah]

Let me close this ticket for now, as it looks like it went stale.