Vincent Batts
Vincent Batts
@AkihiroSuda it seems to be stalled on https://github.com/opencontainers/artifacts/pull/15
it was intentionally vague as that annotations field for runtime state was literally a holding bin so that implementations would just dump arbitrary values across the state. I'm not inclined...
the state annotations were different from the bundle annotations. On 4/4/18 6:12 PM, W. Trevor King wrote: > On Wed, Apr 04, 2018 at 10:03:03PM +0000, Vincent Batts wrote: >...
:-1: I'm okay with this being vague and not imposing a workflow here
was just coming to comment, and saw that Lasker said similar. Making these annotations as first-class keys, I do not think this workflow will ultimately provide the flexibility desired. If...
To be clear, you are saying that the .wh approach is limited? And the whiteout file is preferred? If so, I agree. On Thu, Apr 14, 2016, 17:16 Timothy Hobbs...
I wholly agree and intend to see it done as a whiteout file list. On Thu, Apr 14, 2016, 17:26 Timothy Hobbs [email protected] wrote: > Creating a list of files...
Interesting. There is an option of approaching whiteouts like overlayfs does, by setting device to 0 on non-directories and and xattr for directory. On Mon, Oct 17, 2016, 18:37 Adrian...
so, recording the tool and version that built/assembled the image is interesting, but having it as a pre-defined key is not quite a requirement. Some of these kinds of keys...
this would be useful info though. I'm torn.