Aleksa Sarai
Aleksa Sarai
In general, the OCI deals with already-tested-in-the-field technologies (at least that's what recent discussions about distribution have led me to believe). While having a discussion with us is definitely encouraged...
@wking > I don't think this applies to this proposal. I think you missed the second part of that point, which is that (unrelated to BEAST), taking advantage of deduplication...
As an aside, regarding this: > Require state readers to follow bundle to the config.json if they wanted configured annotations (or embed the whole config.json in the state). One of...
@timthelion No _breaking_ technical changes.
While I think @timthelion is being a bit melodramatic with his examples, I agree with his general point. Why are we treating a **rejected filesystem's serialisation format** (AUFS) as the...
@caniszczyk can set this up.
I would argue distribution-spec would be the best place to do this (and #781) -- since it's not really an issue outside of registries. With "OCIv2" the depth of references...
> I think runtimes should always fail create in those cases, since they can't apply the configured settings (arguably already covered by this spec language). I'm most in favour of...
While I understand why `readonlyPaths` might be okay to ignore (though I'd be worried about the security implications -- really I think an empty file or empty directory should be...
I'm not sure that that this is correct though -- it depends what a user expects and what people want to use masking for. If we're told to mask a...