imeoer

The related code: https://github.com/containerd/nydus-snapshotter/blob/88a72d945ce529053463e1095651402bd4b3822b/pkg/converter/convert_unix.go#L952 (nydusify imported the nydus-snapshotter/pkg/converter package).

@Fricounet Try the `nydusify convert --merge-platform --source $OCI_IMAGE --target $NYDUS_IMAGE` command. :)

@Fricounet I think we should enable the `nydus.remoteimage.v1` flag only for `--merge-platform`, instead of index conversion.

@Fricounet Thanks, the [PR](https://github.com/DataDog/nydus-snapshotter/pull/3) looks good to me, feel free to submit it upstream, maybe we can only add some usage doc. :)

@Fricounet If a node has the nydus snapshotter installed and configured, it will run the nydus image, otherwise it will run the OCI v1 image, is that correct?

@Fricounet How about making it compatible like: ``` json { "schemaVersion": 2, "manifests": [ { "mediaType": "application/vnd.oci.image.manifest.v1+json", "digest": "sha256:4e4bc990609ed865e07afc8427c30ffdddca5153fd4e82c20d8f0783a291e241", "size": 943, "platform": { "architecture": "amd64", "os": "linux" } }, {...

@Fricounet Currently no runtime (snapshotter) supports `os.features: nydus.remoteimage.v1` except for build tools (e.g., nydusify), so I suggest changing it to `artifactType`.

Hi @Fricounet, as far as I know: - `enable_nydus_overlayfs = true`: enable kata guest to access the rootfs of nydus image shared via the host's rootfs using nydusd daemon's virtiofs...

Hi @erezzarum It seems the `endpoint`, `region`, `bucket_name` fields is required.

@erezzarum Sorry for the misunderstand, it seems the error is from nydus-snapshotter, the related codes:  The nydusd component now supports the S3 backend, but the snapshotter has not yet...