imeoer
imeoer
Hi @KristoferHansson, the ctr does not support running nydus image, as it not to pass necessary image info labels to the remote snapshotter, try using nerdctl instead.
Storing blobs in the external backend has indeed introduced many new issues, so perhaps we should consider removing the support of external backend.
Thanks! Could you help submit a PR to fix this? :)
``` kernel: erofs: [deprecated] fscache-based on-demand read feature in use. ``` Is fscache support dropped from EROFS? @hsiangkao
Hi @mmonaco, oci -> nydus conversion has been implemented in `nydusify convert`.
cc Hi @daiyongxuan, could you help take a look at this?
@FengyunPan2 The error "temporarily failed to get blob.meta" likely indicates a network issue to image registry when fetching the blob.meta data segment, try using `nydusify convert --fs-version 5` to convert...
@FengyunPan2 nydusify v2.3.9 included the fixup, rebuilding the image with `nydusify convert ... --fs-version 6` can fix it.
related issue: https://github.com/containerd/nydus-snapshotter/issues/647
Hi @markasoftware-tc, thanks for the PR, we initially considered using the diff approach for the lower and upper dirs, is the `fn Changes` in `contrib/nydusify/pkg/committer/diff/overlay_linux.go`, because it implements stricter and...