Baptiste Girard-Carrabin

@imeoer after doing more tests with this feature, I actually noticed an issue with the way nydus manifests are built currently on certain clients without nydus support. They work fine...

And the change to the config would need to only be applied for images that use `merge-platform`. For the ones with only a nydus manifest, it needs to stay as...

@imeoer So, I digged more into the possible solutions and here's what I got: - the only reliable way I found to have containerd ignore the nydus manifests is to...

@imeoer thanks for the feedback, I'll work on implementing this then. Sorry in advance for all the releases i'll ask of you because we need: - the fix to be...

@imeoer thanks! Here's the acceleration-service PR https://github.com/goharbor/acceleration-service/pull/351

Thanks and here is the final nydusify PR https://github.com/dragonflyoss/nydus/pull/1756

Thanks for all the bumps @imeoer :bow: I've now discovered a new tricky issue though: in the case where 2 OCI images have some layers in common ``` sha256:a606e9d35cbf05763aeb87455d69f3675828408bd4be5cdb9082f8767ef6052a \_...

I believe something cleaner would be that the nydus snapshotter is able to only mount the relevant layer and not the complete original image when containerd calls Mounts but that's...

@imeoer > By the code findIndexAlternativeLayer: Can we only find the index digest and return from the iteration which the snapshot matches i.Labels["containerd.io/snapshot/nydus-bootstrap"] != "" ? The nydus bootstrap (metadata)...

@imeoer Currently I think that the clean way to solve this issue would be to be able to mount intermediate layers. I noticed this [PR](https://github.com/containerd/nydus-snapshotter/pull/447) that was made a while...