-
### Sealos Version
both v4.3.7 and v5.0.0_beta
### How to reproduce the bug?
1. use sealos init install k8s (version such v1.27.1);
2. upgrade version to v1.27.5;
3. add master or node
### What…
-
### 📦 部署环境
- [ ] Official
- [x] Official Preview
- [ ] Vercel / Zeabur / Sealos
- [ ] Docker
- [ ] Other
### 📌 软件版本
0.162.20
### 💻 系统环境
- [X] Windows
- [ ] macOS
- [ ] Ubuntu
- [ ] Other Linux
- …
-
### Sealos Version
v4.3.7
### How to reproduce the bug?
1. sealos reset
2. rm ~/.sealos/ -rf
3. sealos gen docker.io/labring/kubernetes:v1.27.14 --masters 192.168.x.x --pk=$HOME/.ssh/id_rsa -o .…
cnmac updated
4 months ago
-
-
## Sealos Image Update
```
/imagesync imageSourceName
```
-
### Sealos Version
v4.3.7
### How to reproduce the bug?
1. run `sealos add --nodes 10.10.1.1,10.10.1.2`
2. it install fail on 10.10.1.2
3. error ```
W0424 10:09:36.876147 2123 initconfigurati…
-
### Sealos Version
v4.3.5
### How to reproduce the bug?
1. sealos run labring/kubernetes:v1.25.14-4.3.5
### What is the expected behavior?
installation success
### What do you see in…
-
## Sealos Image Update
```
/imagesync imageSourceName
```
-
### Sealos Version
v4.3.7
### How to reproduce the bug?
sealos add --nodes xxxx --debug
### What is the expected behavior?
_No response_
### What do you see instead?
_No response_
### Operatin…
-
### What is the problem this feature will solve?
runc < 1.1.11 has [CVE-2024-21626](https://github.com/opencontainers/runc/security/advisories/GHSA-xr7r-f8xq-vfvv), a container breakout attack that t…