T K Chandra Hasan
T K Chandra Hasan
How about if we create a tag like verify-rel-notes on specific branch, which creates the release notes and opens an issue on cri-o project so that we devs can confirm...
Have skimmed through the code & also the reference PR and here is what I've decided to do. I'm planning to move the code parts which are related to namespaces...
@dfr Can you take a look at the above approach inorder to avoid rework of segregating platform specific stuffs.
/remove-lifecycle stale
Unit test cases needs to be moved. WIP
/remove-lifecycle stale Working on UTs as we need to write test cases for all the mount related methods
Hey, is this still an issue? I tried today on main branch by removing the arch check, which works fine on aarch64. ``` ++ bats --jobs 4 --tap seccomp_notifier.bats 1..4...
I doubt the binaries are FIPS compliant. What made you look for this? ``` [root@fedora bin]# go tool nm crio | grep FIPS reading crio: no symbol section reading crio:...
On Openshift its fips compliant and you can check the binary yourself using the above commands. For more info https://developers.redhat.com/articles/2022/05/31/your-go-application-fips-compliant# https://github.com/cri-o/cri-o/issues/5256