cri-o: cri-o does not execute hook placed to /etc/containers/oci/hooks.d if not restarted
CRI-O does not execute a hook placed to /etc/containers/oci/hooks.d
if not restarted.
/etc/containers/oci/hooks.d
was/is empty when cri-o was initially started (reboot e.g.).
Steps to reproduce the issue:
- On a running system with cri-o already started create a hook in an empty
/etc/containers/oci/hooks.d
- Create a container that triggers the hook
Describe the results you received: The hook is not executed.
Describe the results you expected: The hook is executed without restarting cri-o.
Additional information you deem important (e.g. issue happens only occasionally):
The hook is only executed when I restart cri-o, otherwise cri-o ignores the hooks in
/etc/containers/oci/hooks.d
.
Output of crio --version
:
crio version 1.13.9-1.rhaos4.1.gitd70609a.el8
Additional environment details (AWS, VirtualBox, physical, etc.):
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 24 (14 by maintainers)
I did not start yet, so feel free to go for it 😃
haha whoops. @samc24 PTAL, I would assign you but github UI isn’t letting me…
And it could be supported by HUP as well 👍
This could be handled similar to how we handle CNI using inotify.