@andriyDev : Important location link is not working..? 🤔

@amino19 Woops! I guess my link extension doesn't work haha, fixed!

Hi. Is this issue open? Can I work on it?

Hi. Is this issue open? Can I work on it?

@jayesh-srivastava : Hi, Thanks for showing interest.
Pl go through the links, mentioned by @andriyDev, & ones you feel comfortable to get started with, give a shot with PR, after self-assigning yourself, by typing /assign 🙂

Okay sure. Thank you so much. I am a new contributor here but will try to work on this.

/assign

Hi @amino19 , I have somewhat understood what needs to be done, basically, I'll have to add crun in the list. Just wanted to ask that what will be its value and is that all that I have to do. Your help will be much appreciated : )

@jayesh-srivastava crun --version gets you the version for crun. The only other thing that needs to be done is update the test to ensure it's actually being output.

https://github.com/kubernetes/minikube/blob/master/test/integration/functional_test.go#L1983

Note that crun --version also output some extra junk (beyond version), but fixed in PR #12085

$ crun --version
crun version 0.20.1.5-925d-dirty
commit: 0d42f1109fd73548f44b01b3e84d04a279e99d2e
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL

The "dirty" thing is some kind of upstream packaging bug, modifying the source before building...

https://build.opensuse.org/package/show/devel:kubic:libcontainers:stable/crun

EDIT: Actually it is showing the commit of the packaging repository: https://gitlab.com/rhcontainerbot/crun

https://gitlab.com/rhcontainerbot/crun/-/commit/925db482ab20e0effd1fdaef1cfb5002019a9b5f (5 commits ahead)

The "commit" shown (for 0.20.1) is from the previous software version (crun 0.20): containers/crun@0d42f11