@jhowardmsft why this change? I actually prefer the way it was :S

I agree, but there's a good reason. When I split out the Container structure into common and platform specific parts, everything is good in go except for the constructor "container:=&Container{field: value, etc}.". Accessors are fine, but the constructor will fail compilation. Hence the need to rework it to be field by field. Sucks, I know. As far as I can tell, it's a limitation in go.

Ohhh I see, what you need is this:

container := &Container{
    CommonContainer: CommonContainer{
        State: NewState(),
    },
    root: daemon.containerRoot(id),
    execCommands: newExecStore(),
}

Ahhhh, lightbulb moment. That makes sense. I just learnt more about go. Will verify and address in the morning, Thanks!

That's fixed. Thanks for the pointer in the right direction :)

Does it mean that -v something:ro will be unsupported on Windows?

For the initial release, yes that is the current plan.