Commit 00ca088 broke starting
process-isolated containers when Root.Path is set in the container spec.
Root.Path is set by clients such as Docker which mount and unmount the
container's root filesystem themselves. Mounting is skipped, which also
skips over setting coi.mountedWCOWLayers. The
hcsoci.createWindowsContainerDocument function unconditionally
dereferences that field, resulting in a nil-dereference panic when
mounting is skipped. Restore the old behaviour by synthesizing the
MountedWCOWLayers when Root.Path is set.

Signed-off-by: Cory Snider <[email protected]>
(cherry picked from commit fa457e6)
Signed-off-by: Brian Goff <[email protected]>

… set (#2620)

When runtime options are non-empty (e.g., SandboxIsolation is set) but
SandboxPlatform is empty, skip the platform validation rather than
failing. The validation only needs to check that the spec and shim
options match when SandboxPlatform is explicitly configured.

containerd's default config (config_windows.go) sets SandboxIsolation=1
for the runhcs-wcow-hypervisor runtime handler but omits SandboxPlatform,
making options non-empty with an empty platform string. This causes
platforms.Parse("") to fail with 'invalid runtime sandbox platform'.

Signed-off-by: Dawei Wei <[email protected]>
(cherry picked from commit 88c818f)

Signed-off-by: Maksim An <[email protected]>