journal is getting spammed with messages implying that some process keeps mounting/unmounting volumes :
déc. 01 16:21:22 jetshift systemd[1]: run-runc-37337a04c41b8486f3063bc6ea0c0b7c0d1948fe1bce8a87d4d8c397cab8d288-runc.Z6FXU5.mount: Succeeded.
-- The unit run-runc-37337a04c41b8486f3063bc6ea0c0b7c0d1948fe1bce8a87d4d8c397cab8d288-runc.Z6FXU5.mount has successfully entered the 'dead' state.
déc. 01 16:21:23 jetshift systemd[3127]: run-runc-668f67b97ac5b1ee0f7aeb2e48c929707c83140ed047715c03f5a9e4feddbc3c-runc.C23hEX.mount: Succeeded.
déc. 01 16:21:23 jetshift systemd[1]: run-runc-668f67b97ac5b1ee0f7aeb2e48c929707c83140ed047715c03f5a9e4feddbc3c-runc.C23hEX.mount: Succeeded.
-- The unit run-runc-668f67b97ac5b1ee0f7aeb2e48c929707c83140ed047715c03f5a9e4feddbc3c-runc.C23hEX.mount has successfully entered the 'dead' state.
déc. 01 16:21:33 jetshift systemd[3127]: run-runc-668f67b97ac5b1ee0f7aeb2e48c929707c83140ed047715c03f5a9e4feddbc3c-runc.NDRX8f.mount: Succeeded.
déc. 01 16:21:33 jetshift systemd[1]: run-runc-668f67b97ac5b1ee0f7aeb2e48c929707c83140ed047715c03f5a9e4feddbc3c-runc.NDRX8f.mount: Succeeded.
-- The unit run-runc-668f67b97ac5b1ee0f7aeb2e48c929707c83140ed047715c03f5a9e4feddbc3c-runc.NDRX8f.mount has successfully entered the 'dead' state.
déc. 01 16:21:43 jetshift systemd[3127]: run-runc-668f67b97ac5b1ee0f7aeb2e48c929707c83140ed047715c03f5a9e4feddbc3c-runc.0rkXT6.mount: Succeeded.
déc. 01 16:21:43 jetshift systemd[1]: run-runc-668f67b97ac5b1ee0f7aeb2e48c929707c83140ed047715c03f5a9e4feddbc3c-runc.0rkXT6.mount: Succeeded.
-- The unit run-runc-668f67b97ac5b1ee0f7aeb2e48c929707c83140ed047715c03f5a9e4feddbc3c-runc.0rkXT6.mount has successfully entered the 'dead' state.

microshift rc2

Always

1. Start Microshift
2. Examine the output of journalctl -x | egrep -w 'runc|crun' | wc -l

log being spammed with mount/dead messages

not sure ?

Customer is basically asking if those messages are to be expected and if so if we could reduce their amount so as not to fill up the storage of edge device with such logs