star Jay

I want to know why this happen, If i need to use some external tools? @justadogistaken

> @starComingup Is there the rootfs exists in my-cluster? Check if the rootfs is expected. @justadogistaken where can i found the image layer in my machine? And I make sure...

> ``` > Usage: > sealer run [flags] > > Examples: > > create cluster to your bare metal server, appoint the iplist: > sealer run kubernetes:v1.19.8 --masters 192.168.0.2,192.168.0.3,192.168.0.4 \...

This is my build dir @justadogistaken ```bash . ├── amd64 │   ├── bin │   │   ├── containerd-rootless-setuptool.sh │   │   ├── containerd-rootless.sh │   │   ├── crictl │   │   ├── k0s │  ...

> @starComingup Which branch you are using? Do you push your code? @justadogistaken https://github.com/sealerio/sealer/pull/1686

Using clusterfile can successfully exec next step! It seems that the error exists in apply.go https://github.com/sealerio/sealer/blob/e971bc8fa8eb48d1aec4d8e475476a5ec6bf8faa/apply/apply.go#L80 https://github.com/sealerio/sealer/blob/e971bc8fa8eb48d1aec4d8e475476a5ec6bf8faa/apply/apply.go#L111 run cmd cann't set Annotation, so when there is no Annotation, read error...

If you WSL remained the file `kubeadm.yml`, could you show it to us? @xiaozitwo ```shell cat /var/lib/sealer/data/my-cluster/rootfs/etc/kubeadm.yml ```

I use `go mod tidy`, but it seems so many dependencies imported.

> What is more, I think we could add a design document about different cluster runtime support into the sealer docs directory, which could also be a follow-up pull request....

Thanks for your feature request @gyliu513 . And after I view the vcluster introduce. It may just dependent a bin file like vcluster? In my opinion, you may just focus...