-
Notifications
You must be signed in to change notification settings - Fork 362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] sealer run failed #1702
Comments
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. |
This is the all log? |
@justadogistaken where can i found the image layer in my machine? And I make sure about rootfs existed in my build dir. |
All log pasted here 😭 |
This is my build dir @justadogistaken .
├── amd64
│ ├── bin
│ │ ├── containerd-rootless-setuptool.sh
│ │ ├── containerd-rootless.sh
│ │ ├── crictl
│ │ ├── k0s
│ │ ├── kubectl
│ │ └── nerdctl
│ ├── cri
│ │ └── containerd.tar.gz
│ ├── images
│ │ └── registry.tar.gz
│ └── Metadata
├── arm64
│ ├── bin
│ │ ├── conntrack
│ │ ├── containerd-rootless-setuptool.sh
│ │ ├── containerd-rootless.sh
│ │ ├── crictl
│ │ └── nerdctl
│ ├── cri
│ └── images
├── download.sh
├── imageList
├── Kubefile
├── rootfs
│ ├── etc
│ │ ├── dump-config.toml
│ │ └── registry.yml
│ ├── lib64
│ │ ├── libseccomp.so.2
│ │ └── libseccomp.so.2.5.1
│ └── scripts
│ ├── clean.sh
│ ├── containerd.sh
│ ├── init-registry.sh
│ └── init.sh
└── version.sh
|
@starComingup Which branch you are using? Do you push your code? |
|
+1, I met the same issue. I think there is some bug in the current main branch. |
Using clusterfile can successfully exec next step! It seems that the error exists in apply.go Line 80 in e971bc8
Line 111 in e971bc8 run cmd cann't set Annotation, so when there is no Annotation, read error occurred. Annotation like: metadata:
annotations:
ClusterfileName: /root/k0s-test/Clusterfile It caused GetAnnotaionsByKey read mistake. Line 67 in e971bc8
|
@kakaZhou719 @Stevent-fei FYI. |
@kakaZhou719 |
What happen?
I built my clusterImage with latest code which using buildah , and run my cluster failed.
sealer build -f Kubefile -t registry.cn-hangzhou.aliyuncs.com/starcoming/k0s:v1.24.4 . sealer run registry.cn-hangzhou.aliyuncs.com/starcoming/k0s:v1.24.4 --masters xxxxx --nodes xxxxxx -p xxxxx --cluster-name k8s-test
but got error with
2022-09-13 17:05:03 [ERROR] [root.go:77] sealer-unknown: read .: is a directory
Relevant log output?
What you expected to happen?
run this cluster successfully.
How to reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
I used
sealer inspect registry.cn-hangzhou.aliyuncs.com/starcoming/k0s:v1.24.4
to show image info.What is the version of Sealer you using?
{"gitVersion":"unknown","gitCommit":"a4872762","buildDate":"2022-09-13 00:04:18","goVersion":"go1.17.13","compiler":"gc","platform":"linux/amd64"}
What is your OS environment?
Ubuntu 20.04.5 LTS
What is the Kernel version?
Linux sealer 5.4.0-125-generic
Other environment you want to tell us?
The text was updated successfully, but these errors were encountered: