Avi Deitcher

Dang, it does, @AkihiroSuda ? I missed that. So I could put multiple images, as long as each root is in index.json and has the image name? And `ctr image...

@AkihiroSuda I just read through the spec again (prompted by your explanation), both for [image-layout](https://github.com/opencontainers/image-spec/blob/master/image-layout.md) and [annotations](https://github.com/opencontainers/image-spec/blob/master/annotations.md). I also read through the various extended discussions on this in the issues....

I saw that note @AkihiroSuda , which had me wondering most about that part. This brings me back to the question, which I highlighted above. How would the image-layout format...

Also @AkihiroSuda did I get the rest of it right, in terms of what `index.json` is meant to be? Even if the image root is an index, the `index.json` itself...

Also @AkihiroSuda I renamed the issue, once you explained that it _does_ support them, but it is a question of how. If I need to rename it again after your...

I did not @sudo-bmitch . In cases where I have total control over how the image-layout is produced and consumed, I do what was listed above: ```json "org.opencontainers.image.ref.name": "docker.io/library/alpine:3.11" ```...

I _really_ like this solution. I especially like the configurability of the node labels, rather than tying it down too tightly. If there were some k8s standard for these kinds...

Hi all, any updates on this?

@johananl I am testing now. I have two questions about the implementation. * refresh * peers ### Refresh In the current structure, the config is updated constantly by having a...

> We reconcile the node peer in two cases: when a Node changes and when the ConfigMap changes. The former is handled by SetNode() and the latter by SetConfig(). OK,...