Improve Debugging UX: Push ocihook Logs to Syslog

[fahedouch]

Description

Currently, the logs generated by nerdctl internal oci-hook <event> are not displayed in the containerd logs. This appears to be because the ocihook command runs in a separate shell, causing the logs to be lost.

This makes debugging issues in the ocihook implementation challenging, as there is no straightforward way to access these logs.

Steps to reproduce the issue

1- trigger nerdctl internal oci-hook <event> by run or create a container 2- logs are not printed to console

Describe the results you received and expected

Logs from ocihook should be pushed to syslog for better accessibility and debugging.

Benefits:

• Enhanced visibility into ocihook operations.
• Easier debugging of issues related to ocihook.
• Improved developer experience when working with nerdctl.

What version of nerdctl are you using?

main

Are you using a variant of nerdctl? (e.g., Rancher Desktop)

None

Host information

No response

[AkihiroSuda]

SGTM, but what about having nerdctl logs --full to show the full logs including OCI hooks

[fahedouch]

SGTM, but what about having nerdctl logs --full to show the full logs including OCI hooks

You mean write oci logs to json files and then retrieve them with nerdctl logs --full ?

[yashkukrecha]

Hi! Me, @ShivanshNikhra, and @aravsrid are a group of three students working on open-source issues for our virtualization course. We’re interested in taking on this issue and coordinating the work among ourselves to submit a single PR.

We estimate we can complete it within the next month. Would it be okay if we proceed with this issue? If you prefer assignments, we’re happy to be assigned as well. Thanks!