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]: not support crun + containerd #2643

Open
cuisongliu opened this issue Aug 7, 2024 · 4 comments
Open

[Bug]: not support crun + containerd #2643

cuisongliu opened this issue Aug 7, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@cuisongliu
Copy link

What happened?

using containerd + crun running operator

Steps to reproduce

install containerd + crun

kubectl logs -f -n observability   jaeger-operator-cc7d8bd9c-b9d4w
exit status 2

Expected behavior

running operator in crun and containerd runtime

Relevant log output

No response

Screenshot

No response

Additional context

No response

Jaeger backend version

No response

SDK

No response

Pipeline

No response

Stogage backend

No response

Operating system

No response

Deployment model

No response

Deployment configs

No response

@cuisongliu cuisongliu added the bug Something isn't working label Aug 7, 2024
@iblancasa
Copy link
Collaborator

Hi! Thanks for reporting. Can you provide more information? Would you like yo send a PR?

@cuisongliu
Copy link
Author

When I use crun to run the cluster, the operator cannot run normally and even the log cannot be queried.
containerd version : 1.7.18
crun version 1.15

but , use runc. It runs normally, but it doesn't work when using crun. Is there any limitation in the code that causes this problem? Or is it causing a crun bug?

@iblancasa
Copy link
Collaborator

I don't think there should be anything related to the code.

Can you try to build the container image in your environment and run it in your cluster?

@cuisongliu
Copy link
Author

I don't think there should be anything related to the code.

Can you try to build the container image in your environment and run it in your cluster?

There should be no problem with the docker image . In the same environment, I can switch runc to run normally. Is it related to relying on underlying libraries such as cgroup?

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

No branches or pull requests

2 participants