-
Notifications
You must be signed in to change notification settings - Fork 82
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
config.go:Drop local rootfs.type validation #85
Conversation
On Thu, Nov 17, 2016 at 12:09:44AM -0800, Zhou Hao wrote:
This is checked in the JSON Schema since errors.Wrapf(err, "%s: config validation failed", path) will give you a message about the invalid rootfs.type without us |
I think if the type validation fails or need a separate error message, because in accordance with the provisions of the meaning, the error message should be more detailed. |
On Thu, Nov 17, 2016 at 05:38:49PM -0800, Zhou Hao wrote:
The JSON Schema error from the current master looks like: $ git checkout origin/master That's pretty specific. It doesn't link to the relevant spec line, |
Signed-off-by: zhouhao <[email protected]>
acaa8e3
to
3aaa0b8
Compare
So to say, this type of authentication is not necessary |
The diff for 3aaa0b8 looks good to me, although the commit message
should probably be updated to something like:
config.go: Drop local rootfs.type validation
This is handled in image-spec since opencontainers/image-spec#358
(v1.0.0-rc2).
|
In this type of authentication is not required, because the json file has been identified type value ,if not the case, it will never perform type validation.
Signed-off-by: zhouhao [email protected]