Kohei Tokunaga

> Currently there are [docs](https://github.com/containerd/stargz-snapshotter/blob/main/docs/overview.md#authentication) related to how to access private registries for the snapshotter with containerd, but I couldn't find any reference on how to achieve the same with...

CRI-O will support registry authentication for stargz store since https://github.com/containers/image/pull/2417. That patch was already merged to c/image and I'm waiting for that being downstreamed to CRI-O. If you can wait...

Thanks! Could you sign your commit? (i.e. Add `Signed-off-by` line to your commit message)

That is actually discussed in stargz-snapshotter repo. What we're trying to do is to create a child `*fs.Inode` using `NewInode()` in the parent's `Lookup` method implementation. This `Lookup` implementation shares...

> How about I delay the call to OnAdd until after addNewChild? Then you can make the new or recycled node visible to the rest of your system in an...

> Can you have a look at https://review.gerrithub.io/c/hanwen/go-fuse/+/1200132 ? Would that work for you? Thanks. Overall looks good to me. It would also be great if the user can register...

@hanwen Thanks, it looks good to me.

Currently, I'm working on the lazy-pulling filesystem(FUSE) based on this approach internally. First I've implemented it without "the manifest of tar headers" experimentally and it works but I think we...

FYI: There are similar kind of discussion recently, which is aiming to achieve lazy-pull with preserving compatibility. - https://github.com/golang/go/issues/30829 - https://github.com/google/crfs

Thanks for looking into this! Currently, we are mainly working on [containerd/stargz-snapshotter](https://github.com/containerd/stargz-snapshotter) but we are welcome for the contribution to this project. I think creating [casync](https://github.com/systemd/casync)/[desync](https://github.com/folbricht/desync)-based new [remote snapshotter](https://github.com/containerd/containerd/issues/3731) is...