-
Notifications
You must be signed in to change notification settings - Fork 670
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
conversion: add platform conversions #711
conversion: add platform conversions #711
Conversation
In b6d5a8c ("Change platform ref from runtime-spec"), the conversion to runtime-spec for the "os" and "architecture" fields was removed (as the fields had also been removed in runtime-spec). Re-add the conversion as an annotation field rather than a verbatim field. Signed-off-by: Aleksa Sarai <asarai@suse.de>
/ping @opencontainers/image-spec-maintainers -- this really should've gone into |
Nothing controversial here, but can these be |
I don't think they can be a MUST. |
Are we not allowed to MUST new features in new releases? Also, this document's "MUST" language refers to the "default generated runtime configuration" which in principle could be modified to remove these annotations -- so a runtime that does the wrong thing here isn't non-compliant. |
LGTM @cyphar Not sure if these can be a MUST, still. |
conversion: add platform conversions LGTMs: @jonboulle @stevvooe Closes #711
In b6d5a8c ("Change platform ref from runtime-spec"), the
conversion to runtime-spec for the "os" and "architecture" fields was
removed (as the fields had also been removed in runtime-spec). Re-add
the conversion as an annotation field rather than a verbatim field.
[Obviously this can't go into
1.0.0
due to the time window, but we can put it in1.0.1
].Signed-off-by: Aleksa Sarai asarai@suse.de