shimv2: use the runtime config file passed from containerd/cri

[lifupan]

containerd/cri's different runtime handlers can pass different
config files to shimv2 by a generic runtime options, by this kata
can launch the pods using different VMM for different runtime handlers.

Fixes:#1082

Signed-off-by: Fupan Li lifupan@gmail.com

[gnawux]

env var and the protobuf field, which should have higher privilege?

[lifupan]

env var and the protobuf field, which should have higher privilege?

protobuf > env var > /etc dir > /usr/share/defualt dif

[gnawux]

I have another question with protobuf. if work with old version of containerd, will shimv2 panic due to the lack of a field?

[lifupan]

I have another question with protobuf. if work with old version of containerd, will shimv2 panic due to the lack of a field?

No, it will check the pointer first as below:
if r.Options != nil {

For the old version containerd, here the r.Options will be nil.

[lifupan]

/test

[lifupan]

/test

[gnawux]

lgtm

[lifupan]

@grahamwhaley Is there any thing wrong with CI, the tests have been launched a day ago, but none of them has been scheduled?

[gnawux]

/retest
try again

[grahamwhaley]

hi @lifupan - yep, there was a problem yesterday when a disk filled up and things got stalled/backed up in the queu. I think some jobs then got dropped..... looks like the above action has kicked it into action again ...