Liu Bo

@yangxiaolaing Nydus is using a fixed rust tool chain version 1.61.0, can you please check if the warning occurs with rust 1.61.0?

Any problem if we use the derive api in the same PR?

> > Any problem if we use the derive api in the same PR? > > It should be quite a lot of work to use the derive api instead....

@kevinXYin @mofish33 ``` NFO[2022-07-18T19:11:17.469468809-07:00] Mount erofs to /var/lib/containerd/io.containerd.snapshotter.v1.nydus/mnt/2/fs with options fsid=d6cab71527d3c2896573d33d5794d294dfcafab5d2c024361e17e16c85cc76b2 ERRO[2022-07-18T19:11:17.470042090-07:00] failed to mount /2/fs, failed to shared mount: failed to erofs mount: mount erofs: failed to mount erofs:...

After some debugging, we found out that erofs mount point remained alive after nydus snapshotter terminated, so after nydus snapshotter restarted, the first container's running would bail out because it...

Besides this, nydusify also does not support a registry which has self signed certificate. We'll fix it together.

@changweige can you please take a look?

Is this work done yet?

> I think if the relationship can be enforced then yes, using `tag` or something that can be easily modified is not very reliable. @reasonerjt There is an on-going artifact...

@Champ-Goblem By looking at the https://github.com/dragonflyoss/image-service/blob/v2.1.0-rc.3.1/src/bin/nydusd/virtiofs.rs#L78, I think the workload such as git clone is using mmap and dio, which causes the above panic. ``` fd1 = open("/mnt/virtiofs/foo"); fd2 =...