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]安装runtimeproxy失败 #1580

Closed
ghostloda opened this issue Aug 25, 2023 · 4 comments
Closed

[BUG]安装runtimeproxy失败 #1580

ghostloda opened this issue Aug 25, 2023 · 4 comments

Comments

@ghostloda
Copy link

What happened:
kubelet启动失败:
CRI v1 runtime API is not implemented for endpoint \"unix:///var/run/koord-runtimeproxy/runtimeproxy.sock

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • App version: 1.3.0
  • Kubernetes version (use kubectl version): v1.26.2
  • Node environment (for koordlet/runtime-proxy issue):
    • Containerd: v1.6.19
    • OS version: centos7.9
    • Kernal version: 5.12.0
    • Cgroup driver: systemd
  • Others:
@ghostloda ghostloda added the kind/bug Create a report to help us improve label Aug 25, 2023
@saintube
Copy link
Member

saintube commented Aug 26, 2023

/area runtime-proxy
/area koordlet
Duplicate with #1051.

Sorry. The current version of runtimeproxy does not support CRI v1 API (>= k8s 1.26.0). It will be fixed in the following versions.

There is an alternative of using NRI (Node Resource Interface), which allows k8s 1.26 while requiring containerd >= 1.7.0. Please see this link if you are interested.

@hormes
Copy link
Member

hormes commented Sep 2, 2023

It will be fixed by #1593.

Copy link

stale bot commented Dec 1, 2023

This issue has been automatically marked as stale because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the issue is closed
    You can:
  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Close this issue or PR with /close
    Thank you for your contributions.

@stale stale bot added the lifecycle/stale label Dec 1, 2023
Copy link

stale bot commented Jan 1, 2024

This issue has been automatically closed because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the issue is closed
    You can:
  • Reopen this PR with /reopen
    Thank you for your contributions.

@stale stale bot closed this as completed Jan 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants