decode spec in ctr c info#2688
Conversation
Signed-off-by: Lifubang <[email protected]> fix some errors use typeurl.UnmarshalAny instead json.Unmarshal to interface{} Signed-off-by: Lifubang <[email protected]> Signed-off-by: Michael Crosby <[email protected]>
853c680 to
cb0eed8
Compare
Codecov Report
@@ Coverage Diff @@
## master #2688 +/- ##
======================================
Coverage 45% 45%
======================================
Files 92 92
Lines 10114 10114
======================================
Hits 4552 4552
Misses 4842 4842
Partials 720 720
Continue to review full report at Codecov.
|
|
LGTM |
|
I think the decoded |
Maybe, just make a |
Either is fine to me, but if we reuse the existing e.g. "types.containerd.io/opencontainers/runtime-spec/1/Spec" -> "types.containerd.io/opencontainers/runtime-spec/1/Spec/Decoded" |
|
I think ya'll are making this more complicated than it needs to be. All this does is "dereference" the value and prints it out in ctr. This is for UX/display, nothing more. |
|
any update on this pr? I think it is good to move on. 😄 |
Closes #2568
Signed-off-by: Lifubang [email protected]
Before this commit, the Spec.value field are incomprehensible:
After the commit, there are some useful information for us: