We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
v5.0.0
sealos run as shown in doc
sealos run registry.cn-shanghai.aliyuncs.com/labring/kubernetes:v1.27.0 registry.cn-shanghai.aliyuncs.com/labring/helm:v3.9.4 registry.cn-shanghai.aliyuncs.com/labring/cilium:v1.13.4 registry.k8s.io/etcd:3.5.6-0 --single
No response
- Sealos version: - Docker version: - Kubernetes version: - Operating system: - Runtime environment: - Cluster size: - Additional information:
The text was updated successfully, but these errors were encountered:
This issue has been automatically closed because we haven't heard back for more than 60 days, please reopen this issue if necessary.
Sorry, something went wrong.
No branches or pull requests
Sealos Version
v5.0.0
How to reproduce the bug?
sealos run as shown in doc
sealos run registry.cn-shanghai.aliyuncs.com/labring/kubernetes:v1.27.0 registry.cn-shanghai.aliyuncs.com/labring/helm:v3.9.4 registry.cn-shanghai.aliyuncs.com/labring/cilium:v1.13.4 registry.k8s.io/etcd:3.5.6-0 --single
What is the expected behavior?
What do you see instead?
No response
Operating environment
Additional information
No response
The text was updated successfully, but these errors were encountered: