Sascha Grunert

@grassdionera unfortunately not, we recently switched to default crun. I'd be happy to move forward to conmon-rs. What do other @cri-o/cri-o-maintainers think?

@xuegege5290 you're right. We require a runtime glibc because of some cgo related dependencies. Alternatively we could build using musl libc, but that's something we decided against a few years...

> > @xuegege5290 you're right. We require a runtime glibc because of some cgo related dependencies. Alternatively we could build using musl libc, but that's something we decided against a...

> We had this happen again (inadvertent upgrade to cri-o this time) and I think what was happening is that when the cri-o package gets updated, it doesn't restart the...

@jafager we already define the systemd macros there: https://github.com/cri-o/packaging/blob/52aa3c2a31ccc9623962e9e338b6585267d6f3f4/templates/latest/cri-o/cri-o.spec#L105-L112 I expect a restart from the `%systemd_postun_with_restart crio.service`. :thinking:

Maybe Rust support for NRI wasm plugins would be beneficial here.

Hey @Inbaraj-S, thank you for the report! We're aware of this bug and are going to release a new version after https://github.com/containers/conmon/pull/505 got merged to address it.

Thank you so much @sywhang!

@sywhang is it possible to get a release binary for v0.3.0? :upside_down_face:

Is it possible to add the release binaries to v0.4.0?