-
Notifications
You must be signed in to change notification settings - Fork 676
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
oci-image-tool: more verbose output #222
Comments
@s-urbaniak If there's anything I can help with this please let me know |
@runcom thanks for the help! Sure, just go ahead, I'll try tackle each of those in parallel with other rkt work. Just let me know if you want to tackle all of them or just a subset. Seem like low-hanging fruits to me. |
@runcom If you just tackle a subnet of them, I'd like to help with the rest |
@s-urbaniak If it need to be done based on #159 ? |
On Tue, Aug 30, 2016 at 07:11:01PM -0700, xiekeyang wrote:
I'm all for avoiding conflicts, but #159 tries to stay away from the My long-term plan was to land #159 and then rewrite the type Validator func(ctx context.Context, engine cas.Engine, ref specs.Descriptor, recursive bool) (errors []string) var Validaters map[string]Validator { But I don't have any work in progress on that front, so there won't be |
This issue was moved to opencontainers/image-tools#22 |
As per https://docs.google.com/document/d/1bsi9JCnmOMSZCDh3VmDCO1m17w1aNexX09naomcpUOs/edit the
oci-image-tool
should have more verbose output, more concretely:Print ...
I did implement the last point ("a list of errors") actually already, so I am wondering what additional requirements are needed here.
/cc @philips
The text was updated successfully, but these errors were encountered: