How to run and bind syslog app running in the container to the host system - Githubissues

fujitatomoya / rcl_logging_syslog

rcl_logging_syslog is alternative logging backend implementation that can be used for ROS 2 application via rcl_logging_interface.

https://github.com/fujitatomoya/rcl_logging_syslog

Apache License 2.0

64 stars 0 forks source link

How to run and bind syslog app running in the container to the host system #27

Closed fujitatomoya closed 1 month ago

fujitatomoya commented 1 month ago

This is not related to the implementation for rcl_logging_syslog, more like a question for the configuration.

Background

ROS 2 application likely runs in the container environment such as docker.
Containers are meant to be running with only your application logic, originally nothing else. besides that, having the system level services in the container would be security concerns, 3rd party application can reach the system permission.

What needs to be done?

Introduce how to bind the rsyslogd running in the host system to the syslog app running in the container application. (in this case, ROS 2 application that uses rcl_logging_syslog) this will be the most performance configuration without any extra configuration for Ubuntu users.
(forwarding methods are already introduced by the example of fluentbit and fluentd demonstration.)

fujitatomoya commented 1 month ago

IMO, we can just bind /dev/log socket to the container.

https://github.com/bminor/glibc/blob/master/bits/syslog-path.h#L26

https://github.com/bminor/glibc/blob/master/misc/syslog.c#L326-L334