Skip to content
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: brief description of the bug #5231

Open
qikaih opened this issue Nov 23, 2024 · 2 comments
Open

BUG: brief description of the bug #5231

qikaih opened this issue Nov 23, 2024 · 2 comments
Labels
kind/bug Something isn't working response-expired

Comments

@qikaih
Copy link

qikaih commented Nov 23, 2024

Sealos Version

v5.0.1

How to reproduce the bug?

sealos run labring/kubernetes:v1.31.0 labring/helm:v3.12.0 labring/calico:v3.24.6 --masters xxx, return error
2024-11-23T17:33:21 info start to init master0...
failed to create new CRI runtime service: validate service connection: validate CRI v1 runtime API for endpoint "unix:///var/run/image-cri-shim.sock": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService
To see the stack trace of this error execute with --v=5 or higher

What is the expected behavior?

No response

What do you see instead?

No response

Operating environment

- Sealos version:
- Docker version:
- Kubernetes version:
- Operating system:
- Runtime environment:
- Cluster size:
- Additional information:

Additional information

No response

@qikaih qikaih added the kind/bug Something isn't working label Nov 23, 2024
@oktfolio
Copy link

any solution?

Copy link

stale bot commented Feb 14, 2025

This issue has been automatically closed because we haven't heard back for more than 60 days, please reopen this issue if necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working response-expired
Projects
None yet
Development

No branches or pull requests

2 participants