Logging drivers enhancement

[fahedouch]

What is the problem you're trying to solve

Target Nerdctl logging drivers:

• none
• json-file : implement log opt with containerd logging driver #959
• local
• journald : Implement journald logging driver #1062
• fluentd : Implement fluentd logging driver #1073
• fluentbit
• syslog

Describe the solution you'd like

Configure logging drivers

Additional context

No response

[Zheaoli]

Maybe I can handle the rest of the task in this issue. @fahedouch would you mind this issue to me?

[fahedouch]

thank you for you request @Zheaoli . I start writing code for journald so let me finish it based on your refacto #1050 . You can enhance the rest of the list

[Zheaoli]

@fahedouch Great! Maybe I can write the fluentd and syslog first. BTW, maybe we need spilt the logger in two parts: the readable logger and the unreadable logger

[fahedouch]

@Zheaoli What do you mean by readable logger and the unreadable logger here ?

[Zheaoli]

Yes, because some of the loggers such as fluentd can not read the log directly after we wrote the log. So I think maybe we need to split the logger by two types

[AkihiroSuda]

Probably we should support using multiple drivers simultaneously. Then we can read/write jsonfiles while writing to fluentd.

[Zheaoli]

Probably we should support using multiple drivers simultaneously. Then we can read/write jsonfiles while writing to fluentd.

SGTM.

[fahedouch]

Probably we should support using multiple drivers simultaneously. Then we can read/write jsonfiles while writing to fluentd.

We are creating a dependency between drivers here; json-file driver issue will impact fluentd driver from nerdctl point of view. This can be voluntary when the user configures generated jsonfiles as fluentd tail input (https://docs.fluentd.org/input/tail)

I think we should implement fluentd driver as a separated LoggerFunc, we can implement one of the fluentd input
using this module https://github.com/fluent/fluent-logger-golang

[fahedouch]

@Zheaoli FYI I start working on local driver.

[Zheaoli]

I have a question, should we make the log driver 100% compatible with Docker? Some of the drivers are easy to implement but hard to E2E tests, such as AWS Cloudwatch log driver or others. @fahedouch @AkihiroSuda