Jiahui
> > @kakaZhou719 Do you have any information about high-frequency operations relevant with sealer rootfs? > > user copy build context to manifests is the most high-frequency operation. > >...
> @bxy4543 "ImageList" is generated from "*.yaml / charts" or written by users? by users
nerdctl will use version 0.19 https://github.com/sealerio/basefs/pull/19/files#diff-de765431ea341e699be597845f89f15d1b9cd29fd0c17198d549395faf5f1b7cR13 @Stevent-fei please help me review and test it, thanks billion (十亿分感谢).
What image to use to run the cluster.
``` [root@iZ7xvfzihsbriwt1vd8km8Z test]# sealer run hytest:1 -d 2022-06-22 17:48:00 [INFO] [local.go:288] Start to create a new cluster: master [172.16.191.229], worker [] 2022-06-22 17:48:00 [DEBG] [default_image.go:73] image hytest:1 already exists 2022-06-22...
maybe we can mount via relative path
we can create short symbolic links of all original data layers in the /var/lib/sealer/overlay2/l/ directory, and use relative paths (os.Chdir) to mount if mountData is greater than pagesize during mount.
The coredns image path is changed to 'core' to ['coredns/coredns'](https://github.com/kubernetes/kubernetes/pull/96429/files#diff-afb644eceb2c0d53027d3e3815f43f489b31b34d18f5402a626f2fbfd4b6eb52R326) in the v1.21 version, and the same is true in our ${rootfs}/etc/kubeadm.yml file for versions above v1.21, but the image...
looks similar to the issue: https://github.com/sealerio/sealer/issues/1401
https://github.com/sealerio/sealer/blob/main/pkg/plugin/utils.go#L37