I think it has to do with the container environment. Some thing are not accessible and you have to allow access to it. If I create a new docker image I am always use a run command[1] that links /dev/log from the host. So you do not need rsyslog in the container. I would not use rsyslog in a container unless it would be for getting remote syslog requests and writing them to persistant storage.
[1] docker run --cap-add NET_BIND_SERVICE -v /dev/log:/dev/log -it test bash -----Original Message----- To: [email protected] Cc: lxy Subject: [rsyslog] Can't create /dev/log in docker implicitly. Hello, guys, I run rsyslogd in docker, and boot it in the docker's RUN cmd, following some other command also. But I found that it can't create /dev/log directly, even after I add "$SystemLogSocketName /dev/log". I used "$AddUnixListenSocket /dev/log" to instead of it. I want to know why? My docker base image is a CentOS, but systemd did not run. Thank you _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
